Providing navigation instructions while device is in locked mode

ABSTRACT

A method of providing navigation instructions in a locked mode of a device is disclosed. The method, while the display screen of the device is turned off, determines that the device is near a navigation point. The method turns on the display screen and provides navigation instructions. In some embodiments, the method identifies the ambient light level around the device and turns on the display at brightness level determined by the identified ambient light level. The method turns off the display after the navigation point is passed.

CLAIM OF BENEFIT TO PRIOR APPLICATIONS

This is a continuation of U.S. patent application Ser. No. 15/003,607,filed Jan. 21, 2016, which is a continuation application of U.S. patentapplication Ser. No. 14/691,523, filed Apr. 20, 2015, now issued as U.S.Pat. No. 9,243,924. U.S. patent application Ser. No. 14/691,523 is acontinuation application of U.S. patent application Ser. No. 13/632,120,filed Sep. 30, 2012, now issued as U.S. Pat. No. 9,052,197. U.S. patentapplication Ser. No. 13/632,120 which claims the benefit of U.S.Provisional Patent Application 61/655,995, filed Jun. 5, 2012; U.S.Provisional Application 61/655,997, filed Jun. 5, 2012; U.S. ProvisionalPatent Application 61/656,015, filed Jun. 6, 2012; U.S. ProvisionalApplication 61/656,032, filed Jun. 6, 2012; U.S. Provisional Application61/656,043, filed Jun. 6, 2012; U.S. Provisional Patent Application61/656,080, filed Jun. 6, 2012; U.S. Provisional Application 61/657,864,filed Jun. 10, 2012; U.S. Provisional Application 61/657,880, filed Jun.10, 2012; U.S. Provisional Patent Application 61/699,842, filed Sep. 11,2012; U.S. Provisional Application 61/699,855, filed Sep. 11, 2012; andU.S. Provisional Patent Application 61/699,851, filed Sep. 11, 2012, andU.S. Provisional Patent Application 61/699,857, filed Sep. 11, 2012. Theabove-mentioned applications are incorporated herein by reference.

BACKGROUND

Many map-based applications available today are designed for a varietyof different devices (e.g., desktops, laptops, tablet devices,smartphones, handheld global positioning system (GPS) receivers, etc.)and for various different purposes (e.g., navigation, browsing, sports,etc.). Most of these applications generate displays of a map based onmap data that describes relative locations of streets, highways, pointsof interest, etc., in the map.

The maps used in such applications are usually two-dimensional (2D) mapsor three-dimensional (3D) maps. However, a large number of theapplications use 2D maps due in part to the processing-intensive demandsof viewing 3D maps. For the same reason, the applications that use 3Dmaps are often slow, inefficient, plain, and/or simple, to the pointthat renders the application useless.

BRIEF SUMMARY

Some embodiments of the invention provide a device that includes anavigation application with several novel features. In some embodiments,the device has a touch-sensitive screen that displays the output of theapplication, and a multi-touch interface that allows a user to providetouch and gestural inputs through the screen to interact with theapplication.

In some embodiments, the novel features of the navigation applicationinclude (1) multiple different views (e.g., a two-dimensionalturn-by-turn view, a three-dimensional turn-by-turn view, an overallroute view, etc.) and smooth transitions between these views during thenavigation, (2) novel user interface (UI) controls for navigation, (3)realistic looking road signs for identifying maneuvers along a navigatedroute, (4) dynamic generation of instructions and directional indicatorsfor road signs and other presentations of the identified maneuvers, (5)informative navigation displays when the navigation application isoperating in the background on the device, (6) novel voice recognitionnavigation guidance, and (7) integration with other routing applicationsavailable on or for the device.

While all these features are part of the navigation application in someembodiments, other embodiments do not employ all of these features inthe navigation application. Also, in some embodiments, the navigationapplication is part of an integrated mapping application that providesseveral other useful operations, including location browsing, mapsearching, and route identifying operations. However, one of ordinaryskill will realize that in other embodiments, the navigation applicationis a stand-alone application that does not include some or all of theseother operations.

Each of the above-described features are described here. As mentionedabove, the navigation application of some embodiments provides multipledifferent views during navigation and smooth transitions between theseviews. In some embodiments, examples of such views include atwo-dimensional (2D) turn-by-turn view, a three-dimensional (3D)turn-by-turn view, and an overall route view. The application in someembodiments generates the turn-by-turn views from a perspectiverendering position within a 3D navigation scene that the device renders.This perspective rendering position in some embodiments is adjustableand can be viewed as a virtual camera that can capture the 3D navigationscene from a variety of different perspectives (e.g., from a variety ofdifferent positions and orientations). Accordingly, in some embodiments,the turn-by-turn navigation is an animated rendering of navigated routethat is rendered from the vantage point of a virtual camera thattraverses along the direction of the route based on the traversaldirection and speed of the user carrying the device, which in someembodiments is captured by directional data (e.g., GPS data,triangulated cell-tower data, etc.) associated with the device.

During navigation, the navigation application of some embodiments allowsa user to change the position of the virtual camera (i.e., the positionfrom which the navigated route is rendered) through gestural input onthe device's screen. Movement of the virtual camera (i.e., movement ofthe position from which the route is rendered) allows the navigationapplication to present alternative 3D view. Some embodiments even usethe virtual camera to render a top-down 2D view for the turn-by-turnnavigation, while other embodiments render the top-down 2D view byzooming in and out of a 2D map.

In some embodiments, the navigation application presents a 3D control(e.g., button) that serves both as a 3D indicator and a 3Dinitiator/toggle. The 3D control is implemented in some embodiments as afloating control that can “float” above the 2D or 3D navigationpresentation when it is needed and “float” out of the presentation whenit is not needed. This control also serves as an indicator that thecurrent view is a 3D view. The 3D control may have different appearances(e.g., colored as grey, black, blue, etc.) to provide differentindications. In some embodiments, the 3D control is grey when 3D data isnot available for the user's current location, black when the 3D data isavailable but the user is currently viewing the map in 2D, and purplewhen the user is viewing the map in 3D mode. In some embodiments, the 3Dcontrol displays an image of a building when the user is at a certainzoom level and provides a “flyover” of the buildings in the area whenselected by the user. It also provides a quick mechanism of getting intoand out of 3D navigation. As further described below, the navigationapplication allows transitions between the 2D and 3D navigation viewsthrough other gestural inputs of the multi-touch interface of thedevice.

The navigation application in some embodiments uses floating controls inorder to keep the on-screen controls to a minimum and thereby display asmuch of the interactive navigation as possible. In some embodiments, thefloating controls are part of a cluster of controls that adapt to thetask at hand by adjusting its contents in an animated fashion when auser moves between different navigation views, or between differentapplication modalities for embodiments in which the navigation is justone of several modalities of another application. This adaptive natureallows the navigation application to optimize for different tasks whilemaintaining a consistent look and interaction model while moving betweenthose tasks.

When the navigation application starts a navigation presentation, theapplication in some embodiments (1) automatically hides the floatingcontrols and a bar (containing other UI controls) on the top of a mapalong which the navigation is displayed, and (2) starts a full-screenturn-by-turn navigation presentation. In this mode, the applicationrestricts touch interaction with the map. In some embodiments, a tap isrequired to access the controls that were automatically hidden. In someembodiments, these controls are adapted towards a full-screen navigationlook, including a prominent display of the estimated time of arrival(ETA) in the bar along the top.

In some embodiments, one of the controls in the top bar is an overviewbutton. By selecting this button at any time during the navigation, auser can seamlessly switch between the full-screen; turn-by-turnpresentation that displays a view optimized for turn-by-turn directions;and an overview presentation that displays a view of the remaining routethat better accommodate browsing.

In some embodiments, the constant set of controls and the in-placetransition in the map provide continuity between the overview mode andthe full-screen mode. These controls also include a control that allowsthe user to end the navigation in either the overview mode orfull-screen model. Some embodiments also allow for a search to beperformed while navigating. For instance, some embodiments provide apull down handle that allows the search field to be pulled into theoverview display while navigating in the overview mode. Alternatively,or conjunctively, some embodiments allow for searches to be performedduring navigation through a voice-recognition input of the device ofsome embodiments. Also, in some embodiments, the application allows auser to perform searches (e.g., voice-initiated and/or text-basedsearches) during turn-by-turn navigation. The navigation application ofsome embodiments also allows navigation to be initiated throughvoice-recognition input of the device.

During navigation, the navigation application of some embodiments alsoallows a user to provide some gestural input without reference to thefloating controls or the top-bar controls. For instance, differentembodiments provide different gestural inputs to adjust the 2D/3D viewduring turn-by-turn navigation. In some embodiments, the gestural inputis a two-finger pinching/spreading operation to adjust the zoom level.This adjustment of the zoom level inherently adjusts the position androtation of the camera with respect to the route direction, and therebychanges the 2D/3D perspective view of the route direction.Alternatively, other embodiments provide other gestural inputs (e.g., afinger drag operation) that change the position of the camera instead ofor in addition to the zoom operation. In yet other embodiments, agestural input (e.g., a finger drag operation) momentarily changes theviewing direction of the camera to allow a user to momentarily glance toa side of the navigated route. In these embodiments, the applicationreturns the camera to its previous view along the route after a shorttime period.

Another novel feature of the navigation application are therealistic-looking road signs that are used during navigation. In someembodiments, the signs are textured images that bear a strongresemblance to actual highway signs. These signs in some embodimentsinclude instructional arrows, text, shields, and distance. Thenavigation application of some embodiments presents a wide number ofsign variants in a large number of different contexts. Also, in someembodiments, the application presents signs in different colorsaccording to the regional norms.

For maneuvers that are close together, the application in someembodiments presents a secondary sign beneath the primary sign. Also, asone maneuver is passed, the navigation application animates the signpassing away with a motion that mimics a sign passing overhead on thehighway. When an upcoming maneuver is approaching, the navigationapplication draws attention to the sign with a subtle animation (e.g., ashimmer across the entire sign).

In some embodiments, the navigation application dynamically generatesinstructions for a road sign and other presentation (e.g., a list view)associated with a navigation maneuver based on the context under whichthe application is displaying the sign or presentation. For a givencontext, the instruction text is chosen by considering factors such asthe available space, the availability of information conveyed by meansother than text (e.g., the availability of voice guidance), thelocalized length of each of the instruction variants, the size of thedisplay screen of the device, etc. By locally synthesizing andevaluating several alternatives, the application can pick an optimalinstruction string in every scenario.

Similarly, the navigation application of some embodiments adaptivelygenerates directional graphical indicators for a road sign and otherpresentation (e.g., a list view) associated with a navigation maneuverbased on the context under which the application is displaying the signor presentation. For instance, when there is sufficient space on a signor presentation for the use of a bigger sign, the navigation applicationof some embodiments identifies a maneuver to perform at a juncture alonga route by using a larger graphical directional indicator that includes(1) a prominent stylized arrow roughly representing the path of thevehicle, and (2) a de-emphasized set of lines and curves correspondingto other elements of the junction. In some embodiments that use thisapproach, a right turn at a T-junction is represented by a large arrowwith a right-angle joined with a smaller, dimmer segment that runsparallel to one of the large arrow's segments. The smaller segment insome embodiments is also pushed off to the side so that the path takenby the vehicle dominates.

Such a representation of a maneuver (that includes a prominent stylizedarrow and a de-emphasized set of lines) provides fairly completeinformation about the maneuver while remaining abstract and easilyunderstandable. However, there may not be sufficient space on the signor other presentation for such a representation in other contexts.Accordingly, for such cases, the navigation application of someembodiments uses an alternate representation of the maneuver that omitsdisplaying the junction and instead only displays an arrow in thedirection of movement.

To generate either the prominent stylized arrow or the simplified arrowfor a juncture maneuver along a route, the navigation application insome embodiments receives from a server a description of the junctureand maneuver. In some embodiments, the server performs an automatedprocess to generate this description based on map data, and providesthis information in terms of compressed, geometric point data. Also, atthe beginning of a route navigation, the server in some embodimentssupplies to the navigation application the description of all juncturesand maneuvers along the route, and occasionally updates this descriptionwhen the user strays from the route and the server computes a new route.

When the navigation application receives the juncture and maneuverdescription, the application of some embodiments initially performs aprocess to simplify the characterization of the juncture and themaneuver, and then uses this simplified characterization to generate theprominent stylized graphical directional indicator for the juncture. Todisplay a maneuver at a juncture, some navigation applications oftenprovide a plain arrow that is not expressed in terms of the juncture anddoes not convey much information, while other navigation applicationsprovide a very detailed representation of the juncture and a complexdirectional representation through this detailed representation. Thus,one existing approach provides very little information, while anotherapproach provides so much information that the information is renderedpractically useless. By generating the prominent stylized directionalindicator based on the simplified description of the juncture, thenavigation application of some embodiments displays a detailedrepresentation of the maneuver at the juncture while eliminating some ofthe unnecessary complexities of the juncture.

In some embodiments, the navigation application provides navigationinstructions while the application is operating in the background andeven while the device is locked. In some embodiments, the device islocked when only a reduced set of controls can be used to provide inputinto the device. For instance, in some embodiments, the locking of thedevice greatly limits the number of inputs that a user can providethrough the touch-sensitive screen of the device.

In some embodiments, voice guidance instructions are one example ofinstructions that can be provided while the navigation application isoperating in the background or while the device is locked. Alternativelyto, or conjunctively with, the voice guidance, the navigationapplication can provide text and/or graphical instructions in at leasttwo modes while operating in the background.

First, the application of some embodiments incorporates in the lockscreen background, a live navigation view (e.g., a turn-by-turn view)that includes text and graphical navigation description in thelock-screen display. With this presentation, the user can see thenavigation instructions while the application is running in thebackground without unlocking the device. In some embodiments, theapplication further refines the lock screen experience by sendingnotifications that would normally occupy the space being taken by thenavigation display to a drawer in the lock-screen display, which in someembodiments is done immediately while in other embodiments is done aftera short time period in which the notification is shown on the lockscreen view. Also, whenever a user unlocks the device, some embodimentsreturn without animation to the navigation display in order to make theexperience seamless.

In some embodiments, the application turns off the lock screennavigation display after a time period if no maneuvers are impending.However, the application in some of these embodiments lights up thescreen when approaching an imminent maneuver and/or new navigationinstructions need to be provided. This is a small amount of timerelative to the duration of each step, so the display of the navigationinstructions does not come at the expense of noticeably degraded batterylife. To enhance the experience, the navigation application in someembodiments activates an ambient light sensor well before the navigationprompt so that the ambient light settings can be used to light thescreen to the correct brightness when it comes time to show thenavigation map.

Second, in some embodiments, the navigation application operates in thebackground even when the device is unlocked. This is the case when thenavigation application operates on a device (e.g., a smartphone) thatexecutes several other applications. In such a device, the navigationapplication would operate in the background when the device ispresenting a view (e.g., a page) that is provided by the operatingsystem of the device or a view that is provided by another applicationon the device.

When the navigation application operates in the background on anunlocked device, the device in some embodiments (1) uses a double-heightstatus bar to indicate the background operation of the navigationapplication when far from an upcoming maneuver, and (2) uses a sign-likenavigation banner that includes dynamically updated distance to amaneuver when approaching a maneuver or when guidance instructions areaudible. Further, the application maintains the sign-like banner untilthe maneuver is complete and suppresses other notifications in thatspace. Selection of either the double-height status bar or thenavigation banner in some embodiments directs the device to switch to anavigation view generated by the navigation application.

The above-described features as well as some other features of thenavigation application of some embodiments are further described below.In the description above and below, many of the features are describedas part of an integrated mapping application that provides novellocation browsing, location searching, route identifying and routenavigating operations. However, one of ordinary skill will realize thatthese novel operations are performed in other embodiments byapplications that do not perform all of these operations, or performother operations in addition to these operations.

The preceding Summary is intended to serve as a brief introduction tosome embodiments of the invention. It is not meant to be an introductionor overview of all inventive subject matter disclosed in this document.The Detailed Description that follows and the Drawings that are referredto in the Detailed Description will further describe the embodimentsdescribed in the Summary as well as other embodiments. Accordingly, tounderstand all the embodiments described by this document, a full reviewof the Summary, Detailed Description and the Drawings is needed.Moreover, the claimed subject matters are not to be limited by theillustrative details in the Summary, Detailed Description and theDrawings, but rather are to be defined by the appended claims, becausethe claimed subject matters can be embodied in other specific formswithout departing from the spirit of the subject matters.

BRIEF DESCRIPTION OF THE DRAWINGS

The novel features of the invention are set forth in the appendedclaims. However, for purposes of explanation, several embodiments of theinvention are set forth in the following figures.

FIG. 1 illustrates an example of a device that executes an integratedmapping application of some embodiments of the invention.

FIG. 2 illustrates an example in terms of three stages of a user'sinteraction with the mapping application to obtain routing directions.

FIG. 3 illustrates how the navigation application of some embodimentsprovides the 3D control as a quick mechanism for entering a 3Dnavigating mode.

FIG. 4 illustrates a device that displays a mapping application as theapplication transitions from a non-immersive map view for map browsinginto an immersive map view for navigation.

FIG. 5 presents a simplified example to illustrate the concept of avirtual camera.

FIG. 6 illustrates that the mapping application of some embodimentschanges the appearance of the 3D control to indicate different 2D and 3Dstates of the map view.

FIG. 7 illustrates switching from 3D mode to 2D mode in someembodiments.

FIG. 8 illustrates the adjustment of the distance of a virtual camera bycontracting and expanding gestures.

FIG. 9 illustrates an embodiment of a camera whose angle can be adjustedby gestures.

FIG. 10 conceptually illustrates a feature provided by the mappingapplication of some embodiments for maintaining the position of avirtual camera within a defined range along an arc.

FIG. 11 illustrates a full screen mode of some embodiments.

FIG. 12 illustrates the navigation application with the controls hiddenand revealed during a phone call on the device in some embodiments.

FIG. 13 illustrates the end of a programmed route in some embodiments.

FIG. 14 illustrates a navigation program ending control in someembodiments.

FIG. 15 illustrates the rotation of a map when a user pushes it sidewaysin some embodiments.

FIGS. 16 and 17 illustrate overview controls in some embodiments.

FIG. 18 conceptually illustrates a processing, or map rendering,pipeline performed by the mapping application of some embodiments inorder to render a map for display at the client device.

FIGS. 19A and 19B conceptually illustrate a state diagram that describesdifferent states and transitions between these states of the integratedmapping, search, and navigation application of some embodiments (e.g.,the application described in the above sections).

FIG. 20 illustrates several GUI scenarios in which such highway shieldsare used in some embodiments.

FIG. 21 illustrates several different scenarios in which the mappingapplication displays different types of graphical indicator arrows tovisually represent maneuvers to a user in some embodiments.

FIG. 22 illustrates several scenarios for the same turn, and how thedifferent arrows might be used for the same turn in some embodiments.

FIG. 23 illustrates an example of the synthesis of differentinstructions for a particular maneuver at a juncture according to someembodiments.

FIG. 24 illustrates several different scenarios in which the mappingapplication displays different examples of the adaptive instructions forthe particular maneuver of the first juncture in a variety of differentsituations.

FIG. 25 illustrates additional scenarios in which the mappingapplication uses the synthesized instruction sets in some embodiments.

FIG. 26 illustrates, over four stages, the animation of some embodimentsfor removing a navigation sign and introducing the next sign.

FIG. 27 illustrates such a shimmer animation over four stages thatillustrate the background of the display as gray, in order to contrastwith the shimmer as it moves across the sign in some embodiments.

FIG. 28 illustrates the display of two signs for maneuvers in quicksuccession over four stages in some embodiments.

FIG. 29 illustrates a user device display when navigation is in processin background in some embodiments of the invention.

FIG. 30 conceptually illustrates a process of some embodiments forproviding directions while a navigation application is running in thebackground.

FIG. 31 illustrates a user interface of some embodiments in whichnavigation instructions are given while the navigation application isrunning in the background of another application.

FIG. 32 illustrates a navigation bar displayed at the top of anapplication in some embodiments.

FIG. 33 illustrates the user interface of a device in some embodimentswhere the device reaches its destination while the navigationapplication is running in the background of another application.

FIG. 34 illustrates interaction between a call status bar and anavigation instruction bar.

FIG. 35 illustrates a device of some embodiments that enters locked modewith the navigation application running in the background and exitslocked mode with the navigation application running in the foreground.

FIG. 36 illustrates a device in some embodiments that enters locked modewith the navigation application running in the foreground and exits thelocked mode with the navigation application still running in theforeground.

FIG. 37 illustrates a navigation application giving directions on alocked device in some embodiments of the invention.

FIG. 38 illustrates the locked mode view of some embodiments when thedevice reaches its destination.

FIG. 39 illustrates a locked view notification system of someembodiments.

FIG. 40 illustrates the viewing of notification messages after unlockinga device in some embodiments of the invention.

FIG. 41 illustrates a process for switching the device screen on whenapproaching a navigation point in some embodiments of the invention.

FIG. 42 illustrates multiple stages that a device goes through when nocommands are given to it while a navigation application runs in thebackground in some embodiments of the invention.

FIG. 43 conceptually illustrates a process of some embodiments forturning on the screen when a notification message is received.

FIG. 44 is an example of an architecture of a mobile computing device ofsome embodiments.

FIG. 45 conceptually illustrates an example of an electronic system withwhich some embodiments of the invention are implemented.

FIG. 46 illustrates a map service operating environment, according tosome embodiments.

DETAILED DESCRIPTION

In the following detailed description of the invention, numerousdetails, examples, and embodiments of the invention are set forth anddescribed. However, it will be clear and apparent to one skilled in theart that the invention is not limited to the embodiments set forth andthat the invention may be practiced without some of the specific detailsand examples discussed.

I. Navigation User Interface

A. Start

The navigation application of some embodiments is part of an integratedmapping application that includes several useful modalities, includinglocation browsing, map searching, route identifying and route navigatingoperations. This integrated application (referred to below as themapping application, the navigation application, or the integratedapplication) in some embodiments is defined to be executed by a devicethat has a touch-sensitive screen that displays the output of theapplication. In some embodiments, this device has a multi-touchinterface for allowing a user to provide touch and gestural inputsthrough the screen to interact with the application. Examples of suchdevices are smartphones (e.g., iPhone® sold by Apple Inc., phonesoperating the Android® operating system, phones operating the Windows 8®operating system, etc.).

FIG. 1 illustrates an example of a device 100 that executes anintegrated mapping application of some embodiments of the invention.This figure also illustrates an example of launching a route navigationin this application. This application has a novel user interface (UI)design that seamlessly and cohesively integrates the controls for eachof its different modalities by using a minimum set of on-screen controlsthat float on top of the content in order to display as much of thecontent as possible. Additionally, this cluster adapts to the task athand, adjusting its contents in an animated fashion when a user movesbetween the different modalities (e.g., between browsing, searching,routing and navigating). This common element with an adaptive natureenables the mapping application to optimize for different tasks whilemaintaining a consistent look and interaction model while moving betweenthose tasks.

FIG. 1 shows six stages 105, 110, 115, 117, 119, 121 of interaction withthe mapping application. The first stage 105 shows the device's UI 120,which includes several icons of several applications in a dock area 125and on a page of the UI. One of the icons on this page is the icon forthe mapping application 130. The first stage shows a user's selection ofthe mapping application through touch contact with the device's screenat the location of this application on the screen.

The second stage 110 shows the device after the mapping application hasopened. As shown in this stage, the mapping application's UI has astarting page that in some embodiments displays (1) a map of the currentlocation of the device and (2) several UI controls arranged in a top bar140, and as floating controls. As shown in FIG. 1, the floating controlsinclude an indicator 145, a 3D control 150, and a page curl control 155,while the top bar 140 includes a direction control 160, a search field165, and a bookmark control 170.

In some embodiments, a user can initiate a search by tapping in thesearch field 165. This directs the application to present an animationthat (1) presents an on-screen keyboard and (2) opens a search tablefull of invaluable completions. This table has some importantsubtleties. When the search field is tapped and before the terms areedited, or when the search field is empty, the table contains a list of“recents,” which in some embodiments are recent searches and routedirections that the user has requested. This makes it very easy toquickly bring up recently accessed results.

After any input on the search field, the table is filled with searchcompletions both from local sources (e.g., bookmarks, contacts, recentsearches, recent route directions, etc.) and remote servers. Theincorporation of the user's contact card into the search interface addsadditional flexibility to the design. When showing recents, a route fromthe current location to the user's home is always offered in someembodiments, while it is offered in the contexts that are deemed to be“appropriate” in other embodiments. Also, when the search term matchesat least part of an address label (e.g., ‘ork’ for ‘Work’), theapplication presents the user's labeled address as a completion in thesearch table in some embodiments. Together these behaviors make thesearch UI a very powerful way to get results onto a map from a varietyof sources. In addition to allowing a user to initiate a search, thepresence of the text field in the primary map view in some embodimentsalso allows users to see the query corresponding to search results onthe map and to remove those search results by clearing the query.

The bookmark control 170 (e.g., button) allows location and routes to bebookmarked by the application. The position indicator 145 allows thecurrent position of the device to be specifically noted on the map. Oncethis indicator is selected, the application maintains the currentposition of the device in the center of the map. In some embodiments, itcan also identify the direction to which the device currently points.

The 3D control 150 is a control for viewing a map or inspecting a routein three dimensions (3D). The mapping application provides the 3Dcontrol as a quick mechanism of getting into and out of 3D. This controlalso serves as (1) an indicator that the current view is a 3D view, (2)an indicator that a 3D perspective is available for a given map view(e.g., a map view that is zoomed out might not have a 3D viewavailable), (3) an indicator that a 3D perspective is not available(e.g., the 3D data is not available for the map region), and (4) anindicator that a flyover animation is available at the given zoom level.The 3D control may provide a different appearance corresponding to eachindication. For instance, the 3D control may be colored grey when the 3Dview is unavailable, black when the 3D view is available but the map isin the 2D view, and blue when the map is in the 3D view. In someembodiments, the 3D control changes to an image of a building when theflyover animation is available for the user's given zoom level andlocation on the map.

The page curl control 155 is a control that allows the application tominimize the number of on-screen controls, by placing certain lessfrequently used actions in a secondary UI screen that is accessiblethrough the page curl control that is displayed on the map. In someembodiments, the page curl is permanently displayed on at least some ofthe map views that the application provides. For instance, in someembodiments, the application displays the page curl permanently on thestarting page (illustrated in the second stage 110) that it provides forallowing a user to browse or search for a location or to identify aroute.

The direction control 160 opens a direction entry page 180 through whicha user can request a route to be identified between a starting locationand an ending location. The third stage 115 of FIG. 1 illustrates thatthe selection of the direction control 160 opens the direction entrypage 180, which is shown in the fourth stage 117. The direction controlis one of three mechanisms through which the mapping application can bedirected to identify and display a route between two locations; the twoother mechanisms are (1) a control in an information banner that isdisplayed for a selected item in the map, and (2) recent routesidentified by the device that are displayed in the search field 165.Accordingly, the information banner control and the search field 165 aretwo UI tools that the application employs to make the transition betweenthe different modalities seamless.

The fourth stage 117 shows that the direction entry page 180 includesstarting and ending fields for providing starting and ending locationsfor a route, and a table that lists recent routes that the applicationhas provided to the user. Other controls on this page are controls forstarting a route, for reversing the order of the start and endlocations, for canceling the direction request, for picking walking,auto, or public transit routes. These controls and other aspects of themapping application are described in U.S. patent application Ser. No.13/632,102 now issued as U.S. Pat. No. 9,052,197, entitled “ProblemReporting in Maps.” U.S. patent application Ser. No. 13/632,102 isincorporated herein by reference.

The fourth stage illustrates the user selecting one of the recentdirections that was auto-populated in the table 182. The fifth stage 119then shows three routes on a 2D map view between the specified start andend locations specified through the page 180. It also shows theselection of the second route and some information about this route in abar at the top of the layout. This bar is shown to include start and endbuttons. The start button is shown to be selected in the fifth stage.

As shown in the sixth stage, the selection of the start button directsthe application to enter a turn-by-turn navigation mode. In thisexample, the application has entered a 2D turn-by-turn navigation mode.In other embodiments, the application will enter by default into a 3Dturn-by-turn navigation mode. In this mode, the application displays arealistic sign 184 that identifies the distance from the currentlocation of the device to the next juncture maneuver in the navigatedroute and some other pertinent information. The application alsodisplays a top bar that includes some information about the navigationas well as End and Overview buttons, for respectively ending thenavigation and obtaining an overview of the remaining portion of thenavigated route or the entire portion of the navigated route in otherembodiments.

The mapping application of some embodiments identifies the location ofthe device using the coordinates (e.g., longitudinal, altitudinal, andlatitudinal coordinates) in the GPS signal that the device receives atthe location of the device. Alternatively or conjunctively, the mappingapplication uses other methods (e.g., cell tower triangulation) tocompute the current location. When the user carrying the device deviatesfrom the route, the mapping application of some embodiments tracks thelocation of the device and re-calculates a new route from the deviatedlocation in order to re-direct the user to the destination location fromthe deviated location. In other words, the mapping application of someembodiments operating in the navigation mode requires the device to beon a route at all times.

The application further displays the floating 3D control and thefloating list control, which were described above. It should be notedthat the list control was adaptively added to the floating controlcluster upon entering the route inspection and route navigationmodalities, while the position indicator was removed from the floatingcontrol upon entering the route navigation modality. Also, upontransition from the route inspection mode to the route navigation mode,the application performs an animation in some embodiments that involvesthe page curl uncurling completely before the application transitionsinto the navigation presentation.

In some embodiments, the animation transition includes removing the topbar, its associated controls and the floating controls from thenavigation presentation, and moving the sign 184 to the top edge of thepresentation a short time period after starting the navigationpresentation. As further described below, the application requires theuser tap on the navigated map to bring back the top bar, its controlsand the floating controls, and requires another tap to remove thesecontrols again from the map, in some embodiments. Other embodimentsprovide other mechanisms for viewing and removing these controls.

As another way of allowing the user to get navigation experience, themapping application of some embodiments provides a UI item in aninformational banner that appears by a pin that represents a point ofinterest (POI). FIG. 2 illustrates an example in terms of three stages205-215 of a user's interaction with the mapping application to obtainrouting directions. This example is provided in the context of using acar icon 230.

The first stage 205 illustrates a map in a 3D map view. As shown, a 3Dcontrol 250 appears highlighted to indicate that the map is in a 3D mapview. The first stage 205 also illustrates two informational banners forthe two pins for the search resulting from running a search with asearch query “Pizza” as shown. The user selects the car icon 230. Asmentioned above, the car icon 230 is for showing one or more routes tothe location that is represented by a pin with which the banner thatincludes the car icon 230 is associated. The banner 240 which includesthe car icon 230 also shows a brief description of the place, a starrating, and an arrow for launching a “stage” for the POI.

The second stage 210 illustrates the two routes, route 1 and route 2,that the mapping application of some embodiments shows in response tothe selection of the car icon 230 in the previous stage 205. The userhas selected route 1 as indicated by the highlight on the route 1. Theuser also selects the start button. As mentioned above, the start buttonin some embodiments is for starting the navigation according to theselected route.

The third stage 215 illustrates that the mapping application displays aninstruction sign 260, which is the sign for the first instruction. Themapping application has replaced the clear control 255 and the startbutton with an end button 270 and an overview control 275 in the top bar140. The end button is for ending the navigation of the route and theoverview control 275 is for showing the entire route in the map view byadjusting the zoom level of the displayed map if adjusting the zoomlevel is necessary to show the entire route. In some embodiments, themapping application displays in the top bar 140 the ETA, the amount oftime to get to the destination, and the remaining distance to thedestination as shown.

When the mapping application receives a selection of the end buttonwhile the mapping application is operating in the route inspection mode,the mapping application of some embodiments stops inspection of theselected route by going back to map browsing mode. The mappingapplication of some embodiments goes back to the map browsing mode byremoving the selected route from the map, putting back the page curl,and replacing the information and controls in the top bar with a set ofother controls including a direction control, a search field, and abookmark control. That is, the mapping application takes the appearanceof the UI page back to a UI page similar to the UI page shown in thefirst stage 205. The mapping application of some embodiments does notshift the map to another region when switching to the map browsing modefrom the inspection mode.

B. 2D and 3D Navigation

The navigation application of some embodiments can display navigation ineither a 2D mode or a 3D mode. As mentioned above, one of the floatingcontrols is the 3D control 250 that allows a user to view a navigationpresentation in three dimensions (3D). FIG. 3 illustrates how thenavigation application of some embodiments provides the 3D control 250as a quick mechanism for entering a 3D navigating mode. This figureillustrates this operation in three stages 305-315. The first stage 305illustrates the user selecting the 3D control 150 while viewing atwo-dimensional navigation presentation.

The second stage 310 illustrates the navigation presentation in themidst of its transition into a 3D presentation. As shown in this figure,the 3D control appears highlighted at this stage to indicate that thenavigation presentation has entered a 3D mode. As mentioned above, thenavigation application generates the 3D view of the navigated map insome embodiments by rendering the map view from a particular position inthe three dimensional scene that can be conceptually thought of as theposition of a virtual camera that is capturing the map view. Thisrendering is further described below by reference to FIG. 5.

The third stage 315 then illustrates the navigation presentation at theend of its transition into its 3D appearance. As shown by the differencebetween the heights of the buildings in the second and third stages, thetransition from 2D to 3D navigation in some embodiments includes ananimation that shows three-dimensional objects in the navigated mapbecoming larger. Generating such animation that shows objectsrising/falling and becoming larger/smaller is further described in theU.S. patent application Ser. No. 13/632,027, now published as U.S.Patent Publication number 2014/0071119, entitled “Displaying 3D Objectsin a 3D Map Presentation.” U.S. patent application Ser. No. 13/632,027is incorporated herein by reference.

Some embodiments use a cinematic transition from the 2D map view to the3D map view or vice versa. For instance, when the mapping applicationreceives a selection of the 3D control 250 while showing a startinglocation of a route, the mapping application begins from the 2D map viewand transitions smoothly from a first virtual camera view for the 2D toa new virtual camera 3D view that is more zoomed in and pointing in thedirection of the start of the route. In doing so, the virtual cameraperforms a combination of translation, zoom, and rotation operations inorder to reach the start of the route for navigation. That is, thevirtual camera moves in an arc and rotates upward as the camera movesdownward along the arc. Also, the mapping application may rotate the arcitself to align the virtual camera viewpoint to the initial road segmentof the route. In other words, the mapping application rotates the mapduring the cinematic transition.

FIG. 4 illustrates a device 400 that displays a mapping application asthe application transitions from a non-immersive map view for mapbrowsing into an immersive map view for navigation, over six stages405-430.

The first stage 405 illustrates a user selecting a quick-route buttonfor a location “Pizza Place” in order to generate a route from theuser's current location (near the center of the screen of device 400) tothe selected location. The second stage 410 illustrates the mappingapplication displaying a route 435 to reach the location “Pizza Place.”At the second stage 410, the user selects the “Start” UI control 440.Accordingly, the application begins entering navigation.

As shown at the third through sixth stages 415-430, some embodiments usea cinematic transition from the 2D (or 3D) non-immersive map view intothe 3D immersive map view. The application display begins from itscurrent state (that shown at 410) and transitions smoothly from thefirst virtual camera view to the new virtual camera view that is morezoomed in and pointing in the direction of the start of the route. Indoing so, the virtual camera may perform a combination of translation,zoom, and rotation operations in order to reach the start of the routefor navigation. As shown in these stages, the virtual camera moves androtates into its eventual location behind the navigation locationindicator (i.e., the puck) shown in the sixth stage 430.

Also, in some embodiments, the mapping application provides twodifferent types of 3D presentations—an immersive 3D presentation and anon-immersive 3D presentation. The immersive presentation in someembodiments not only displays more geometries but also displays moredetails for the geometries that are displayed in the non-immersivepresentation. The mapping application also provides smooth transitionsbetween the non-immersive and immersive presentations.

To achieve such smooth transitions and generate other novel effects, themapping application of some embodiments uses a novel image processingpipeline. This pipeline performs a variety of pre-load operations todownload, retrieve and/or decompress map tiles that may be needed for anavigation presentation, to prepare its rendering pipeline for itsrendering operations, and to prepare a duplicate pipeline to smoothlytransition between the immersive and non-immersive 3D presentations. Inorder to display immersive and non-immersive 3D map presentations, someembodiments have to generate a variety of tiles for client devices torender in order to generate roads, building, and surrounding scenery. Insome embodiments, examples of such tiles include road and building tilesused for non-immersive 3D presentations, and navigation and buildingtiles used for immersive 3D presentations. This pipeline is described inabove-incorporated U.S. patent application Ser. No. 13/632,102, nowpublished as U.S. Patent Publication number 2013/0326407, entitled“Problem Reporting in Maps.”. This pipeline is also described in detailin the U.S. patent application Ser. No. 13/632,040, now issued as U.S.Pat. No. 9,269,178, entitled “Virtual Camera for 3D Maps.”. U.S. patentapplication Ser. No. 13/632,040 is incorporated herein by reference.

In some embodiments, the non-immersive and immersive viewing modes areviewing modes for viewing different 3D maps that have differentconstructs and/or geometries. For instance, the non-immersive viewingmode of some embodiments is for viewing a 3D map that includes roads,buildings, land cover, etc. The immersive viewing mode is for viewing amore detailed 3D map that includes the same or similar elements (e.g.,roads, buildings, land cover, etc.) as the 3D map for the non-immersiveviewing mode. However, this more detailed 3D map also includes higherdetail constructs (e.g., trees, foliage, sidewalks, medians, lanes ofroads, road asphalt, medians, cross walks, etc.) that provide a morerealistic and rich 3D map.

In addition, the non-immersive and immersive viewing modes may bedefined for viewing 3D maps at different ranges of zoom levels. Forexample, the non-immersive viewing mode of some embodiments is definedfor viewing a 3D map at low zoom levels (e.g., zoom levels 0-14) whilethe immersive viewing mode of some embodiments is defined for viewingthe 3D map at high zoom levels (e.g., zoom levels 16-21). The viewingmodes may be defined to view any number of different zoom levels indifferent embodiments. In some instances, the range of zoom levels ofthe immersive viewing mode are defined as higher zoom levels than, lowerzoom levels than, the same zoom levels as, or zoom levels that overlapwith the zoom levels defined for the non-immersive viewing mode. Theseviewing modes and other aspects of the mapping application are describedin the U.S. patent application Ser. No. 13/632,040, now issued as U.S.Pat. No. 9,269,178, entitled “Virtual Camera for 3D Maps.” U.S. patentapplication Ser. No. 13/632,040 is incorporated herein by reference.

1. Virtual Camera

The navigation application of some embodiments is capable of displayingnavigation maps from multiple perspectives. The application can showmaps in three dimensions (3D) or in two dimensions (2D). The 3D maps aregenerated simulations of a virtual scene as seen by a virtual camera.FIG. 5 presents a simplified example to illustrate the concept of avirtual camera 512. When rendering a 3D navigation map, a virtual camerais a conceptualization of the position in the 3D map scene from whichthe device renders a 3D view of the scene. FIG. 5 illustrates a locationin a 3D navigation map scene 510 that includes four objects, which aretwo buildings and two intersecting roads. To illustrate the virtualcamera concept, this figure illustrates three scenarios, each of whichcorresponds to a different virtual camera location (i.e., a differentrendering position) and a different resulting view that is displayed onthe device.

The first stage 501 shows the virtual camera 512 at a first positionpointing downwards at an angle (e.g., a 30 degree angle) towards the 3Dscene 510. By rendering the 3D scene from the position and angle shownin stage 501 the application generates the 3D map view 518. From thisposition, the camera is pointing at a location that is a moving positionin front of the device. The virtual camera 512 is kept behind thecurrent location of the device. “Behind the current location” in thiscase means backward along the navigation application's defined path inthe opposite direction from the current direction that the device ismoving in.

The navigation map view 518 looks as though it was shot by a camera fromabove and behind the device's location indicator 516. The location andangle of the virtual camera places the location indicator 516 near thebottom of the navigation map view 518. This also results in the majorityof the screen being filled with the streets and buildings ahead of thepresent location of the device. In contrast, in some embodiments, thelocation indicator 516 is in the center of the screen, with half of thescreen representing things ahead of the device and the other halfrepresenting things behind the device. To simplify the figure, no roadsigns are depicted for the views 518, 528, and 538.

The second stage 502 shows the virtual camera 512 at a differentposition, pointing downwards towards the scene 510 at a larger secondangle (e.g., −45°). The application renders the scene 510 from thisangle, resulting in the 3D navigation map view 528. The buildings andthe roads are smaller than their illustration in the first navigationmap view 518. Once again the virtual camera 512 is above and behind thelocation indicator 516 in the scene 510. This again results in thelocation indicator appearing in the lower part of the 3D map view 528.The location and orientation of the camera also results again in themajority of the screen displaying things ahead of the location indicator516 (i.e., the location of the car carrying the device), which is whatsomeone navigating needs to know.

The third stage 503 shows the virtual camera 512 at a top-down view thatlooks downwards on a location in the 3D map scene 510 that was used torender the 3D views 518 and 528. The scene that is rendered from thisperspective is the 2D map view 538. Unlike the 3D rendering operationsof the first and second stages that in some embodiments are perspective3D rendering operations, the rendering operation in the third stage isrelatively simple as it only needs to crop a portion of the 2D map thatis identified by a zoom level specified by the application or the user.Accordingly, the virtual camera characterization in this situationsomewhat unnecessarily complicates the description of the operation ofthe application as cropping a portion of a 2D map is not a perspectiverendering operation.

At the third stage 503, the mapping application in some embodimentsswitches from rendering a 3D scene from a particular perspectivedirection to cropping a 2D scene when the camera switches from the 3Dperspective view to a 2D top-down view. This is because in theseembodiments, the application is designed to use a simplified renderingoperation that is easier and that does not generate unnecessaryperspective artifacts. In other embodiments, however, the mappingapplication uses a perspective rendering operation to render a 3D scenefrom a top-down virtual camera position. In these embodiments, the 2Dmap view that is generated is somewhat different than the map view 538illustrated in the third stage 503, because any object that is away fromthe center of the view is distorted, with the distortions being greaterthe further the object's distance from the center of the view.

The virtual camera 512 moves along different trajectories in differentembodiments. Two such trajectories 550 and 555 are illustrated in FIG.5. In both these trajectories, the camera moves in an arc and rotatesdownward as the camera moves upward along the arc. The trajectory 555differs from the trajectory 550 in that in the trajectory 555 the cameramoves backward from the current location as it moves up the arc.

While moving along one of the arcs, the camera rotates to maintain apoint ahead of the location indicator at the focal point of the camera.In some embodiments, the user can turn off the three dimensional viewand go with a purely two dimensional view. For example, the applicationof some embodiments allows a three dimensional mode to be turned on andoff by use of a 3D button 560. The 3D button 560 is essential to theturn-by-turn navigation feature, where it has a role as an indicator anda toggle. When 3D is turned off, the camera will maintain a 2Dnavigation experience, but when 3D is turned on, there may still be sometop-down perspectives when 3D viewing angles are not appropriate (e.g.,when going around a corner that would be obstructed in 3D mode).

2. 3D Control

FIG. 6 illustrates in six different stages 605-630 that the mappingapplication of some embodiments changes the appearance of the 3D controlto indicate different 2D and 3D states of the map view. The first stage605 illustrates that the mapping application is displaying a map and thefloating controls including the 3D control 150. The mapping applicationis displaying the map in 2D at a certain low zoom level (map has notbeen zoomed in much) as shown. The 3D control 150 is displayed using afirst appearance (e.g., grey letters “3D”) to indicate the 3D map datais not available at this particular zoom level. The first stage 605 alsoshows that the mapping application is receiving the user's gesturalinput to zoom in on the map (i.e., to increase the zoom level).

The second stage 610 shows that the mapping application is displayingthe map at a higher zoom level than it did at the previous stage 605.However, the 3D control 150 is maintaining the first appearance becausethe 3D map data is still not available even at this particular higherzoom level. The second stage 610 also shows that the mapping applicationis receiving another gestural input to zoom in on the map further.

The third stage 615 shows that the mapping application is displaying themap at a higher zoom level than it did at the previous stage 610. Themapping application has changed the appearance of the 3D control 150into a second appearance (e.g., “3D” in black letters) to indicate thatthe 3D map data is available at this zoom level. When the mappingapplication receives a selection of the 3D control 150, the mappingapplication of some embodiments would change the appearance of the 3Dcontrol 150 to a third appearance (e.g., “3D” in blue letters) anddisplay the map in 3D (e.g., by changing into a perspective view from astraight-down view for 2D). The third appearance therefore wouldindicate that the map is displayed in 3D. The third stage 615 shows thatthe mapping application is receiving yet another gestural input to zoomin the map even further to a higher zoom level. The third stage 615shows that the mapping application is displaying buildings in the map asgrey boxes at this zoom level.

The fourth stage 620 shows that the mapping application is displayingthe map at a higher zoom level than it did at the previous stage 615.The mapping application has changed the appearance of the 3D control 150into a fourth appearance (e.g., a building icon in a first color asshown) in order to indicate that 3D immersive map data for rendering animmersive 3D map view is available at this zoom level. The fourth stage620 also shows that the mapping application of some embodiments isreceiving a selection of the 3D control 150.

The fifth and sixth stages 625 and 630 show subsequent views (though notnecessarily successive views) that the mapping application providesafter it starts to provide a 3D immersive map view. The zoom level doesnot change between the fifth and sixth stages in some embodiments butthe height of the buildings in the map views increases to provide ananimation that conveys that the view is moving into the 3D immersive mapview from the 2D view. Also, from the fourth stage 620 to the fifthstage 625, the mapping application has changed the appearance of the 3Dcontrol into the fifth appearance (e.g., a building icon in a secondcolor as shown) in order to indicate that the map is displayed in the 3Dimmersive view.

3. Automatic Changing of Views

The application of some embodiments allows any particular virtual cameraangle to be used, not just the 30 degree and 60 degree angles specifiedhere. The application of some embodiments allows the user to set thedownward angle for the camera. The application of some embodimentsautomatically adjusts the angle of the camera for various reasons,(e.g., to keep a particular point of focus near the top of the screen).In still other embodiments, the navigation application automaticallysets the angle of the camera, but allows the user to override theautomatically set angle.

In some embodiments, when a device running the navigation application ina 3D mode is about to reach a junction with a turn, the navigationapplication switches to a 2D mode in order to enable the user to moreclearly identify the turn. FIG. 7 illustrates the switching from 3D modeto 2D mode of some embodiments. The figure is shown in five stages701-705. In stage 701, the application shows a navigation map in a 3Dview. The navigation box 710 shows a right turn in 50 feet. The map 712is in 3D as is the location identifier 714.

As the device approaches the junction in stage 702 (as indicated bynavigation box 720) the 3D map 712 switches to a 2D map 722 with thelocation indicator 724 in 2D as well. The mapping application alsochanges the appearance of the 3D control 150 to indicate that the map isnow in 2D. The map 722 remains in 2D as the device rounds the corner instage 703. As the device rounds the corner, the navigation box 730 withthe instructions “turn right into A St.” in stage 703 is replaced by thenavigation box 740 with the instructions “0.5 miles continue straight onA St.” in stage 704. The map remains in 2D in stage 704 until the cornerhas been fully navigated at which point, in stage 705, the map returnsto a 3D view with new instructions “0.3 miles Destination will be onyour left” in navigation box 750. The mapping application also haschanged the appearance of the 3D control 150 to indicate the map is nowback in 3D.

In some embodiments, the navigation application determines some or allof the following five pieces of information for every location update(e.g., 1 time per second). First, the navigation application determinesthe location of the point of reference (i.e. the user's location).

Second, the navigation application determines the location of the pointof focus of the virtual camera, which is used to determine whichdirection the virtual camera should face. If the user is off-route, thepoint of focus will be a fixed distance ahead of the user along theuser's direction of travel (if that can be determined) or a fixeddistance north of the user (if the user's direction of travel cannot bedetermined). If the user is on-route, the point of focus will be a fixeddistance ahead of the user along the route, with the angle between thevector from the user and this point of focus and the user's traveldirection capped at a maximum value. This allows the virtual camera tosubtly peek around turns before the user actually turns. For example, ifthe route turns a corner shortly ahead, the point of focus will be apoint around the corner from the current location of the device. Asturning the virtual camera to face that actual point could cause thevirtual camera to directly face a building, the virtual camera is cappedas to how far off the present direction it can look. Third, thenavigation application determines the location of the point of interest(e.g., the location of an upcoming intersection).

Fourth, the navigation application determines the virtual camera viewstyle (top-down centered, top-down forward, or rooftop). “Top-downcentered” means that the virtual camera should look straight down on theuser's location such that the user's location is in the center of thescreen. “Top-down forward” means the virtual camera should look straightdown on the user's location such that the user's location is toward thebottom of the screen. “Rooftop” means the virtual camera should bebehind the user's location and pitched so that it is looking forwardalong the vector from the user's location to the point of focus. If theuser is off-route or the user's direction of travel cannot be determined(e.g., when the user is parked), the virtual camera will be in top-downcentered view style. Otherwise, the view style will be determined bywhether the user has requested “2D” navigation or not. If the user hasrequested 2D navigation, the view style will be top-down forward.Otherwise, the view style will be rooftop.

Fifth, the navigation application determines the virtual camera focusstyle (e.g., cruise or hard focus). “Cruise focus style” means thevirtual camera should adopt a preset height and pitch angle based on theview style. “Hard focus” means that the virtual camera should adjust itsheight (in the case of top-down centered or top-down forward viewstyles) or pitch (in the case of rooftop view style) so that the givenpoint-of-interest is just on screen (i.e. the virtual camera shouldfocus in on the point-of-interest as the user approaches it). When farfrom an intersection, the navigation application puts the virtual camerain cruise focus mode. When approaching an ‘interesting’ intersection,the navigation application puts the virtual camera in hard focus mode asdescribed above and the location of the intersection (point of interest)will be passed to the virtual camera. When in hard focus mode, theapplication adjusts the virtual camera's height (in the case of top-downcentered or top-down forward view styles) or pitch (in the case ofrooftop view style) so that the intersection is at a reasonable positionon screen. A given intersection is determined to be ‘interesting’ enoughto focus on using the angle at which the user will leave theintersection. If the angle is large enough (e.g., a 90 degree rightturn), the intersection is considered to be ‘interesting’ and thevirtual camera will focus on it. If the angle is too small (e.g.,merging onto a freeway), the virtual camera will stay in cruise focusstyle

From these five pieces of information, the navigation applicationcomputes the virtual camera's desired position and orientation. From thedesired position and orientation, the positions of the following threekey points can be extracted: (1) the virtual camera's position, (2) theintersection between the virtual camera's forward vector and the ground,and (3) a point along the virtual camera's right vector. The threepoints are animated independently from each other as follows: (1) when anew point is available, the application fits a cubic polynomial betweenthe last evaluated position/tangent for that point and the new point and(2) every step of the animation, the navigation application evaluatesthe cubic polynomials for each curve and extracts the virtual cameraposition and orientation from them.

4. User Adjustment of Camera Height

Besides (or instead of) having the navigation application control thecamera (e.g., turning from 3D to 2D when going around corners) someembodiments also allow the user to adjust the level of the camera. Someembodiments allow the user to make a command gesture with two fingers toadjust the distance (height) and angle of the camera. Some embodimentseven allow multiple types of gestures to control the camera. FIG. 8illustrates the adjustment of the distance of a virtual camera bycontracting and expanding gestures. The figure is shown in three stages801-803. In stage 801, the application shows a basic scene 810 with avirtual camera 812 at the default level for 3D viewing and the screenview 814 rendered from the scene 810. The basic scene contains twobuildings and a T-junction. In stage 801, the buildings are viewed froma 45 degree downward angle and a particular height that makes them seema particular size. The location indicator 816 is also shown at aparticular size.

In stage 802, the user makes a gesture by placing two fingertips neareach other on the screen of the device, on the screen view 824 andmoving the fingertips apart while they are on the screen. Moving thefingertips apart has the effect of making the map (both the part betweenthe fingers and the rest of the map) larger. In order to make the thingsin the map appear larger, the application causes the virtual camera 812to zoom in. In some embodiments, the line 850 that the mappingapplication uses to move the virtual camera 812 along is a line formedby the front of the virtual camera 812 and the virtual camera 812'spoint of focus. The mapping application of some embodiments moves thevirtual camera 812 along a line formed by the front of the virtualcamera 812 and a location in the 3D map 810 based on the user's input tozoom into the view of the 3D map 810.

After zooming in for stage 802, the user decides to zoom out for stage803. In this stage the user has placed two fingers on the screen andbrought them closer together. Bringing the fingers closer together hasthe effect of shrinking the map (both the part between the fingers andthe rest of the map). The zoom-out adjustment is accomplished by movingthe virtual camera 812 moving farther away from the 3D map 810 along theline 855. In some embodiments, the line 855 that the mapping applicationuses to move the virtual camera 812 along is a line formed by the frontof the virtual camera 812 and the virtual camera 812's point of focus.The mapping application of some embodiments moves the virtual camera 812along a line formed by the front of the virtual camera 812 and alocation in the 3D map 810 based on the user's input to zoom into theview of the 3D map 810.

Rendering a 3D map view using the virtual camera 812 at this positionresults in a 3D map view 834 in which the buildings and the roads appearfarther than the position illustrated in the 3D map view 824. As shownby the dashed-line version of the virtual camera 812, the virtual camera812 moved farther from the 3D map 810 along the line 855.

In addition to being controllable by zooming in and out, someapplications allow a user to change the angle of the virtual camera.FIG. 9 illustrates an embodiment of a camera whose angle can be adjustedby gestures. The figure is shown in three stages 901-903. In stage 901,the camera is pointing downward at 45 degrees at scene 910. Scene 910contains two buildings and a T-junction which are shown in screen view914. The buildings are shown from a particular angle and a particularsize. The location indicator 916 is also shown at a particular size.

In stage 902, the user has placed two fingers 920 on the screenapproximately horizontal to each other and dragged up. This has theapparent effect of dragging the scene up with the fingers. The scenerising is accomplished by the virtual camera 912 lowering and changingits viewing angle from 45 degrees to 30 degrees. In the screen view 924,the buildings and the location indicator look taller than in stage 901.

After the user drags the scene up in stage 902, the user then drags thescene down in stage 903. To do this, the user again placed two fingers930 on the screen and drags them down. This drags the scene down alongwith the fingers 930. The scene dropping is accomplished by the virtualcamera 912 rising and changing its angle with the scene 910 to 60degrees downward. In stage 903, the camera 912 has moved farther up andis angled down more than in stage 901. Accordingly, the buildings andlocation identifier 916 again look shorter and smaller in stage 903 thanin stage 901.

In some embodiments, the mapping application provides an inertia effectfor different operations (e.g., panning, rotating, entering from 2D to3D). When a user provides a particular type of input (e.g., input thatterminates at a velocity greater than a threshold velocity) to pan the3D map, the mapping application generates an inertia effect that causesthe 3D map to continue panning and decelerate to a stop. The inertiaeffect in some embodiments provides the user with a more realisticinteraction with the 3D map that mimics behaviors in the real world.Details of inertia effects and implementations of inertia effects aredescribed in U.S. patent application Ser. No. 13/632,040, now issued asU.S. Pat. No. 9,269,178, entitled “Virtual Camera for 3D Maps.” U.S.patent application Ser. No. 13/632,040 is incorporated herein byreference.

The application of some embodiments allows the distance and angle of thecamera to be independently controlled. For example, it allows thedistance to be controlled by the contracting and expanding fingergestures and the angle to be controlled by the dragging of horizontallyplaced fingers. Other embodiments use whichever gesture is beingperformed to set either a distance or an angle of the camera, with theother variable being set automatically. While FIGS. 8 and 9 showgestures being performed in a certain direction leading to certainresults, in some embodiments, one or both of these gestures could bereversed. For example, in some embodiments, dragging horizontally placedfingers down may bring the camera down rather than bringing the scenedown. That would have the effect of moving the scene down when thefingers move up and moving the scene up when the fingers move down.

FIG. 10 conceptually illustrates a feature provided by the mappingapplication of some embodiments for maintaining the position of avirtual camera within a defined range along an arc. In particular, FIG.10 illustrates the virtual camera 1000 at three different stages1005-1015 that show the virtual camera 1000's position maintained withina defined range of arc 1050. As shown in FIG. 10, a location in a 3D map1035 includes two buildings and two roads forming a T-junction.

The first stage 1005 shows the virtual camera 1000 at a particularposition along the arc 1050. As shown, the arc 1050 represents a definedrange (e.g., angular range) within which the virtual camera 1000 ismovable. The first stage 1005 also shows three positions 1055-1065 alongthe arc 1050 (e.g., perspective view angles). In this example, themapping application moves the virtual camera 1000 along the arc 1050between the high perspective end of the arc 1050 (e.g., the positionalong the arc 1050 when the virtual camera 1000 is most tilteddownwards) and the position 1055 in a manner similar to that describedabove by reference to FIG. 9. Rendering a 3D map view based on thevirtual camera 1000's position in the first stage 1005 results in 3D mapview 1025.

When the virtual camera 1000 passes the position 1055 while movingtowards the low perspective end of the arc 1050, the mapping applicationreduces the speed (e.g., decelerates) that the virtual camera 1000 movestowards the low perspective end of the arc 1050 regardless of the inputprovided by a user. In some embodiments, the mapping application reducesthe speed of the virtual camera 1000 at a constant rate while, in otherembodiments, the mapping application reduces the speed of the virtualcamera 1000 at an exponential rate. Additional and/or different methodsfor decreasing the speed of the virtual camera 1000 are used in someembodiments.

The second stage 1010 shows that the virtual camera 1000 has moved to aposition along the arc 1050 at or near the low perspective end of thearc 1050. As shown, a user is providing input to adjust the perspectiveof the view of the 3D map 1035 by touching two fingers on the screen anddragging the two fingers in an upward direction (e.g., a swipe gesture).In response to the input, the mapping application moved the virtualcamera 1000 toward the low perspective end of the arc 1050 while tiltingthe virtual camera 1050 upwards. When the virtual camera reaches theposition 1065 along the arc 1050, the mapping application prevents thevirtual camera 1000 from moving lower and beyond the position 1065 evenwhile the user continues to provide input to decrease the perspective ofthe view of the 3D map 1035 (e.g., the user continues to drag the twofingers upwards on the touchscreen).

In some embodiments, when the user stops providing input to decrease theperspective of the view of the 3D map 1035 (e.g., the user lifts the twofingers off the touchscreen), the mapping application “bounces” or“snaps” the position of the virtual camera 1000 from the position 1065up to the position 1060 along the arc 1050. As the mapping applicationis generating or rendering 3D map views of the 3D map 1035 based on theview of the virtual camera 1000 during the bounce or snap motion, thegenerated 3D map views provide a bounce animation that displays the 3Dmap view briefly bouncing or snapping down in order to indicate to theuser that the perspective of the map view cannot be decreased anyfarther. Rendering a 3D map view using the virtual camera 1000positioned at this angle results in a 3D map view 1030 in which thebuildings and the roads are taller compared to the map view 1025.

The third stage 1015 shows the virtual camera 1000 after the mappingapplication has bounced or snapped the position of the virtual camera1000 to the position 1060 in response to the user ceasing to provideinput. Different embodiments use different techniques for implementingthe bounce or snap of the virtual camera 1000. For instance, the mappingapplication of some embodiments starts quickly accelerating the virtualcamera 1000 along the arc 1050 for a defined distance or until thevirtual camera 1000 reaches a defined speed. Then the mappingapplication decelerates the virtual camera 1000 for the remainingdistance to the position 1060 along the arc 1050. Other ways toimplement the bounce or snap effect are used in some embodiments.Rendering a 3D map view using the virtual camera 1000 positioned at theposition 1060 along the arc 1050 in the third stage 1015 results in a 3Dmap view 1040 in which the buildings appear a little smaller and flatterand the roads appear a little smaller compared to the map view 1030.

As described above, FIG. 10 illustrates a technique for preventing avirtual camera from moving beyond the low perspective end of an arc.Alternatively or in conjunction with preventing the virtual camera frommoving beyond the low perspective end of the arc, the mappingapplication of some embodiments utilizes a similar technique forpreventing the virtual camera from moving beyond the high perspectiveend of the arc. In addition, FIG. 10 shows an example of a positionalong an arc at which to slow down a virtual camera, a position alongthe arc to prevent the virtual camera from moving past, and a positionalong the arc to which the virtual camera snaps or bounces back.Different embodiments define the positions any number of different ways.For instance, in some embodiments, the position along the arc at whichto slow down the virtual camera is the same or near the position alongthe arc to which the virtual camera snaps or bounces back.

C. Other User Interactions

1. Appearing and Disappearing Controls

The applications of some embodiments, while navigating, have a fullscreen mode. That is, during the actual providing of directions, thecontrols that ordinarily take up some of the screen surface are hidden.FIG. 11 illustrates a full screen mode of some embodiments. The figureis shown in six stages 1101-1106. In stage 1101 a set of navigationinstructions is activated by the selection of a start button 1110. Byselecting the start button, the user selects the highlighted route fromtwo possible routes. The non-highlighted route disappears, and a smallerscale navigation map 1121 appears in stage 1102. The first stage 1101shows that the road names are on the roads because the mappingapplication is displaying a map view. The first stage 1101 also showsthat the position control 1130 is displayed for the mapping applicationis displaying a map view. The selection of the list control 1132 willcause the mapping application to display the available routes in a listformat.

Also in stage 1102, the first instruction 1120 is shown along with anend control 1122, trip status area 1124 (including an ETA, a tripduration estimate, and a distance of planned route indicator), anoverview button 1126, status bar 1127, and a 3D control 1128. The endbutton 1122 ends the running of the navigation instructions. The statusarea 1124 displays information about the planned route. The overviewbutton 1126 displays an overview of the route. The 3D control is anindicator of whether the navigation application is showing a scene in 3Dor 2D and a toggle for entering and leaving 3D mode. The selection ofthe list control 1132 at this stage will cause the mapping applicationto display the set of navigation instructions in a list format. Thisstage also shows that the road names are displayed in banners ratherthan on the roads because the mapping application is operating in thenavigation mode.

After a brief amount of time, the end control 1122, the list control1132, status area 1124, overview button 1126, and 3D control 1128disappear. In some embodiments, the controls disappear abruptly, whilein other embodiments the controls fade away. In some embodiments, thestatus bar 1127 at the top of the screen also vanishes and navigationbox 1120 moves to the top of the screen.

The absence of the controls and movement of navigation box 1120 is shownin stage 1103, in which the navigation map 1121 is seen without thecontrols except for the raised navigation box 1120. The user can restorethe hidden controls by tapping the screen in some embodiments. This isdemonstrated in stages 1104 and 1105. In stage 1104, the user taps thescreen with finger 1140. In stage 1105, as a result of the tap in theprevious stage, the controls are back and the navigation box 1120 hasdropped back down to its original position. The restored controlsinclude end control 1122, status area 1124, overview button 1126, statusbar 1127, and 3D control 1128. Once the controls are back, the user canmake the controls vanish again by tapping, as shown in stage 1105 wherea user taps the screen with finger 1150 to restore the navigationapplication to full screen mode in stage 1106. In addition to the hiddencontrols, in full-screen in some embodiments the touch interaction withthe map is greatly restricted. In some embodiments, more controls existthat are shown in some modes, but hidden in full screen mode (e.g., alist control).

In some embodiments, when the controls are shown and there is anaddition to the status bar (e.g., a phone call status bar showing thelength of an ongoing call) the navigation box is shortened in order tomake more room for the expanded status bar. This is shown in FIG. 12,which illustrates the navigation application with the controls hiddenand revealed during a phone call on the device. FIG. 12 includes stages1201 and 1202. In stage 1201 the controls of the navigation applicationare hidden and the navigation box 1210 and map 1215 are visible. Theuser taps on the touchscreen with finger 1217 to command the navigationapplication to show its controls. In stage 1202, the navigationapplication shows its controls 1220 and also shows a phone call statusbar 1222 under the status bar 1224. The navigation application has lessroom due to the phone call status bar 1222. To compensate for thesmaller amount of screen area available to the navigation application,the navigation application of some embodiments shrinks the navigationbox 1210 when the phone call status bar 1222 is on the screen. In someembodiments, when the navigation box shrinks, the text and/or directionarrow in the box is altered to fit the reduced amount of area availablefor the text and arrow.

2. Ending Navigation

In the ordinary course of the running of a set of navigationinstructions by a navigation application, as the device reaches each newjunction that needs navigation instructions, the instructions for thenext such junction appear. This continues until the device reaches itsdestination. When the destination is reached, the navigation applicationstops providing instructions and the running of the programmed routeends. FIG. 13 illustrates in four stages 1301-1304 the end of aprogrammed route. In stage 1301, the application is running with hiddencontrols and the navigation box 1310 is showing that the destination isonly 1000 feet away. The destination is shown on the map as a pin 1312with a round head. However, one of ordinary skill in the art willunderstand that other symbols could be used in applications of otherembodiments and that in some embodiments no symbol is used and the linemerely ends. As the device moves closer to its destination, thenavigation application counts down the distance. In stage 1302, thenavigation box 1320 shows that there are only 100 feet to go to thedestination. In stage 1303, the device has just reached its destination.Navigation box 1330 indicates that the destination is on the left andincludes a symbol of an arrow pointing at the center of a target. Later,in stage 1304, with the device having reached its destination, thenavigation application has shut navigation box 1320 down leaving theuser with a map 1340, but no further directions.

In some embodiments, destinations can be in places not reachable by car,for example, the end pin could be in the middle of a park. In some suchembodiments, the driving directions will end, but there will becontinued directions for foot travel. In other such embodiments, theapplication will not give textual directions for travel on foot, butwill still maintain a pin on the location (e.g., the middle of a park)when displaying maps in map mode or in locked mode. In some suchembodiments, the last instruction after the automotive portion of thejourney ends will be a direction “please reach on foot”.

FIG. 13 illustrates what happens when a navigation application guidesthe user all the way to its final destination. However, in someembodiments, the user may change the user's mind about gettingdirections. The user may want to stop along the way, changedestinations, or for some other reason, may want to end the running ofthe set of navigation instructions. Accordingly, the application of someembodiments includes an “end” button. The end button stops the runningof a set of navigation instructions and in some embodiments leaves theuser in the same condition as if they had reached the destination (e.g.,no instructions but with a map). FIG. 14 illustrates a navigationprogram ending control. The figure is shown in two stages 1401 and 1402.Stage 1401 shows a navigation application with its controls visible. Thecontrols include an “end” button 1410. The user is tapping the buttonwith finger 1412. The navigation application is far from itsdestination, as indicated by navigation box 1414, which states that thenext junction is 20 miles away, and by route 1416, which stretches offinto the distance ahead of position indicator 1418. In stage 1402,because the user has tapped the end button 1410, the navigation box 1414disappears as does the route 1416. The position indicator 1418 is alsogone in this stage, replaced by a spherical position indicator 1428.

3. Gestures to Look to the Side of the Route During Navigation

As described above, the default behavior for the virtual camera is tofollow the location of the device through a virtual world and point downand in the direction the device is moving, or at least to a part of itsroute a short way ahead of the device's present position. However, it isnot always desirable to have the camera pointing straight ahead.Sometimes the user wants the camera to point at an angle instead.Accordingly, the navigation application of some embodiments rotates thevirtual camera around when the user drags the map sideways.

FIG. 15 illustrates the rotation of a map when a user pushes itsideways. The figure includes four stages 1501-1504. In stage 1501, theapplication is shown in its default mode, with the street 1510 (MainSt.) and the current route 1512 running parallel to the sides of thescreen on the 3D map 1514. In this stage 1501 the user begins pushingthe map to the left. In the next stage 1502, the virtual camera hasmoved to the left and rotated to the right. That is, the 3D map 1514 haschanged as though the virtual camera has moved to the left and rotatedto the right. The map 1514, having been rotated, now shows the faces ofthe buildings on the right side of the street. In some embodiments,there is a maximum threshold to how far the map will rotate. In someembodiments, as well as being able to move the map from side to side,the user can move to a view slightly ahead of or slightly behind thelocation indicator (e.g., by dragging down or up with one finger). Insome such embodiments, the amount that the map can be moved ahead orbehind by dragging is also capped.

In the illustrated embodiment, the application only rotates thebuildings while the user is dragging the map to the left (or right), orfor a short time after (e.g., with simulated inertia). Once the userstops dragging the map 1514 or holding his finger in place to hold themap 1514 in place, the map 1514 reverts to its default view in thedirection of the route the camera is taking. This is shown in stage 1503in which the user has stopped dragging the map 1514 and the virtualcamera is rotating and/or moving back to its original position directlybehind the device as it moves on its route. By stage 1504, the map 1514has resumed its previous orientation. In some embodiments, the virtualcamera merely rotates when the map is dragged sideways, rather thanmoving as well as rotating. While in other embodiments, the camerarevolves around the location identifier so that the location identifierappears to be a fixed point while the map revolves around it.

4. Route Overview Mode

In some cases, rather than looking at only a small scale map that showsthe next junction, some users may sometimes want to get a look at thebig picture. That is, the users may want to look at the entirety oftheir navigation application's planned route while the user is travelingover the route. Therefore some embodiments provide an overview optionthat shows the user the entire route. FIGS. 16 and 17 illustrateoverview controls. FIG. 16 includes two stages 1601 and 1602. In stage1601 a navigation map 1610, overview button 1612, finger 1614, and listcontrol 1617 are shown. In navigation map 1610, the location indicator1616, shows that the device is on Main St. close to 1st St. The stage1601 also shows that the mapping application is displaying the roadnames in banners 1618 because the mapping application is operating inthe navigation mode. In this stage the finger 1614 hits overview button1612 causing the overview to be displayed in stage 1602.

In stage 1602, the navigation application has displayed an overview map1620, resume button 1622, location indicator pin 1626, end pin 1628 andposition indicator control 1630. The overview map 1620 shows the userhis entire planned route starting from the present position. In theillustrated embodiment, the overview map focuses on the remaining route,not the entire route from the beginning, as it does not show a lightcolored line indicating the previously traveled route. However, in someembodiments, the overview map shows the entire route rather than justthe route from the current location of the device. In some embodiments,list control 1617 is also present in the overview map to allow the userto go directly from the overview map to a list of maneuvers (e.g.,upcoming turns). The second stage 1602 also shows that the road namesare displayed on the road because the mapping application is displayingthe overview map (i.e., not in the navigation mode). It is to be notedthat the mapping application of some embodiments alternatively orconjunctively uses banners to display the road names regardless of themode in which the mapping application is operating.

The resume button 1622 switches the navigation application back to thenavigation view of stage 1601. The location indicator pin 1626 and theend pin 1628 show the current location of the device and the finaldestination of the navigation route, respectively. In some embodiments,the application allows a user to move the map around, zoom in and out,and otherwise focus on different parts of the overview map 1620. Theposition indicator control 1630 in some embodiments centers the map onthe location indicator pin 1626.

In some embodiments, the overview mode has a search box that allows auser to enter search queries for items that may be found in the overviewmap. For example, the user could search for gas stations on the map sothat the user can determine where to refuel his car. Another examplewould be a search for coffee shops so the user could stop for coffee.Some embodiments allow a user to switch from an original end destinationto a destination found in a search before resuming navigation.

In some embodiments all overview maps are 2D. In other embodiments, someor all overview maps are in 3D. For example, some embodiments use 2Doverview maps for routes that cover large distances, but use 3D overviewmaps for navigation routes that cover short distances. FIG. 17illustrates an embodiment that uses 3D overview maps. FIG. 17 includestwo stages 1701 and 1702. In stage 1701 a navigation map 1710, overviewbutton 1712, finger 1714, and list button 1617 are shown. In navigationmap 1710, the location indicator 1716 shows that the device is on MainSt. close to 1st St. In this stage the finger 1714 hits overview button1712 causing the overview to be displayed in stage 1702.

In stage 1702, the navigation application has displayed an overview map1720, resume button 1722, location indicator pin 1726, end pin 1728 andposition indicator control 1730. The overview map 1720 shows the usertheir entire planned route. The resume button 1722 switches thenavigation application back to the navigation view of stage 1701. Thelocation indicator pin 1726 and end pin 1728 show the current locationof the device and the final destination of the navigation route,respectively. The position indicator control 1730 centers the map on thelocation indicator pin 1726.

In some embodiments, the 3D overview maps include a search function asdescribed with respect to FIG. 16. Also, in some embodiments, theoverview mode includes a control to center the map on the end pin. Insome embodiments, the position indicator control allows a user to togglebetween centering on the present location of the device and thedestination of the device. In some embodiments, the overview mode can beactivated at any time while navigating.

D. Multi-Mode Application

1. Rendering Module

FIG. 18 conceptually illustrates a processing, or map rendering,pipeline 1800 performed by the mapping application of some embodimentsin order to render a map for display at the client device (e.g., on thedisplay of the client device). In some embodiments, the map renderingpipeline 1800 may be referred to collectively as a map rendering module.A more detailed version of this processing pipeline is described in U.S.patent application Ser. No. 13/632,040, now issued as U.S. Pat. No.9,269,178, entitled “Virtual Camera for 3D Maps.” U.S. patentapplication Ser. No. 13/632,040 is incorporated herein by reference. Asillustrated, the processing pipeline 1800 includes tile retrievers 1805,a set of mesh builders 1815, a set of mesh building processors 1810, atile provider 1820, a virtual camera 1830, and a map rendering engine1825.

The tile retrievers 1805 perform various processes to retrieve map tilesin some embodiments, according to requests for the map tiles from themesh builders 1815. The mesh builders 1815, as will be described below,identify existing map tiles (that are stored on a mapping service serveror in a cache on the device performing the processing pipeline 1800)needed to build their respective meshes. The tile retrievers 1805receive the requests for the map tiles, determine the best location fromwhich to retrieve the map tiles (e.g., from the mapping service, from acache on the device) and decompress the map tiles if required.

The mesh builders 1815 (also referred to as tile sources) of someembodiments are instantiated by the tile provider 1820 in order to builddifferent layers of view tiles. Depending on the type of map beingdisplayed by the mapping application, the tile provider 1820 mayinstantiate a different number and different types of mesh builders1815. For instance, for a flyover (or satellite) view map, the tileprovider 1820 might only instantiate one mesh builder 1815, as theflyover map tiles of some embodiments do not contain multiple layers ofdata. In fact, in some embodiments, the flyover map tiles contain analready-built mesh generated at the mapping service for which theflyover images (taken by a satellite, airplane, helicopter, etc.) areused as textures. However, in some embodiments, additional mesh buildersmay be instantiated for generating the labels to overlay on the flyoverimages when the application is in a hybrid mode. For a 2D or 3D renderedvector map (i.e., a non-satellite image map), some embodimentsinstantiate separate mesh builders 1815 to build meshes for landcoverpolygon data (e.g., parks, bodies of water, etc.), roads, place ofinterest markers, point labels (e.g., labels for parks, etc.), roadlabels, traffic (if displaying traffic), buildings, raster data (forcertain objects at certain zoom levels), as well as other layers of datato incorporate into the map.

The mesh builders 1815 of some embodiments, receive “empty” view tilesfrom the tile provider 1820 and return “built” view tiles to the tileprovider 1820. That is, the tile provider 1820 sends to each of the meshbuilders 1815 one or more view tiles (not shown). Each of the view tilesindicates an area of the world for which to draw a mesh. Upon receivingsuch a view tile, a mesh builder 1815 identifies the map tiles neededfrom the mapping service, and sends its list to the tile retrievers1805.

Upon receiving the tiles back from the tile retrievers 1805, the meshbuilder uses vector data stored in the tiles to build a polygon mesh forthe area described by the view tile. In some embodiments, the meshbuilder 1815 uses several different mesh building processors 1810 tobuild the mesh. These functions may include a mesh generator, atriangulator, a shadow generator, and/or a texture decoder. In someembodiments, these functions (and additional mesh building functions)are available to each mesh builder, with different mesh builders 1815using different functions. After building its mesh, each mesh builder1815 returns its view tiles to the tile provider 1820 with its layer ofthe mesh filled in.

The tile provider 1820 receives from the controller 1875 a particularview (i.e., a volume, or viewing frustrum) that represents the map viewto be displayed (i.e., the volume visible from the virtual camera 1830).The tile provider performs any culling (e.g., identifying the surfacearea to be displayed in the view tile), then sends these view tiles tothe mesh builders 1815.

The tile provider 1820 then receives the built view tiles from the meshbuilders and, in some embodiments, performs culling on the built meshusing the particular view from the virtual camera 1830 (e.g., removingsurface area too far away, removing objects that will be entirely behindother objects, etc.). In some embodiments, the tile provider 1820receives the built view tiles from the different mesh builders atdifferent times (e.g., due to different processing times to completemore and less complicated meshes, different time elapsed beforereceiving the necessary map tiles from the tile retrievers 1805, etc.).Once all of the layers of view tiles have been returned, the tileprovider 1820 of some embodiments puts the layers together and releasesthe data to the controller 1875 for rendering.

The virtual camera 1830 generates a volume or surface for the pipeline1800 to render, and sends this information to the controller 1875. Basedon a particular location and orientation from which the map will berendered (i.e., the point in 3D space from which the user “views” themap), the virtual camera identifies a field of view to actually send tothe tile provider 1820. In some embodiments, when the mappingapplication is rendering the 3D perspective view for navigation, thefield of view of the virtual camera is determined according to analgorithm that generates a new virtual camera location and orientationat regular intervals based on the movement of the user device.

The controller 1875 is responsible for managing the tile provider 1820,virtual camera 1830, and map rendering engine 1825 in some embodiments.In some embodiments, multiple tile providers may actually beinstantiated, and the controller puts together several view tiles (e.g.,map tiles and building tiles) to create a scene that is handed off tothe map rendering engine 1825.

The map rendering engine 1825 is responsible for generating a drawing tooutput to a display device based on the mesh tiles (not shown) sent fromthe virtual camera. The map rendering engine 1825 of some embodimentshas several sub-processes. In some embodiments, each different type ofmap element is rendered by a different sub-process, with the renderingengine 1825 handling the occlusion of different layers of objects (e.g.,placing labels above or behind different buildings, generating roads ontop of land cover, etc.). Examples of such rendering processes include aroad rendering process, a building rendering process, a label renderingprocess, a vegetation rendering process, a raster traffic renderingprocess, a raster road rendering process, a satellite rendering process,a polygon rendering process, a background raster rendering process, etc.

The operation of the rendering pipeline 1800 in some embodiments willnow be described. Based on user input to view a particular map region ata particular zoom level, the virtual camera 1830 specifies a locationand orientation from which to view the map region, and sends thisviewing frustrum, or volume, to the controller 1875. The controller 1875instantiates one or more tile providers. While one tile provider 1820 isshown in this figure, some embodiments allow the instantiation ofmultiple tile providers at once. For instance, some embodimentsinstantiate separate tile providers for building tiles and for maptiles.

The tile provider 1820 performs any culling necessary to generate anempty view tile identifying regions of the map for which a mesh needs tobe built, and sends the empty view tile to the mesh builders 1815, whichare instantiated for the different layers of the drawn map (e.g., roads,land cover, POI labels, etc.). The mesh builders 1815 use a manifestreceived from the mapping service that identifies the different tilesavailable on the mapping service server (i.e., as nodes of a quadtree).The mesh builders 1815 request specific map tiles from the tileretrievers 1805, which return the requested map tiles to the meshbuilders 1815.

Once a particular mesh builder 1815 has received its map tiles, itbegins using the vector data stored in the map tiles to build the meshfor the view tiles sent from the tile provider 1820. After building themesh for its map layer, the mesh builder 1815 sends the built view tileback to the tile provider 1820. The tile provider 1820 waits until ithas received all of the view tiles from the various mesh builders 1815,then layers these together and sends the completed view tile to thecontroller 1875. The controller stitches together the returned tilesfrom all of its tile providers (e.g., a map view tile and a buildingview tile) and sends this scene to the rendering engine 1825. The maprendering engine 1825 uses the information in the map tiles to draw thescene for display.

2. State Diagram for Different Modes

FIG. 19 conceptually illustrates a state diagram 1900 that describesdifferent states and transitions between these states of the integratedmapping, search, and navigation application of some embodiments (e.g.,the application described in the above sections). One of ordinary skillin the art will recognize that the application of some embodiments willhave many different states relating to all different types of inputevents, and that the state diagram 1900 is specifically focused on asubset of these events. The state diagram 1900 describes and refers tovarious gestural interactions (e.g., multi-touch gestures) for changingstates of the application. One of ordinary skill in the art willrecognize that various other interactions, such as cursor controllergestures and button clicks, keyboard input, touchpad/trackpad input,etc., may also be used for similar selection operations.

When a user initially opens the mapping application, the application isin state 1905, the map browsing state. In this state 1905, theapplication will have generated and displayed a map view. To generateand display this map view, the application of some embodimentsidentifies a required set of map tiles for a region, requests the maptiles (e.g., from a mapping service server), generates a view of the maptiles from a particular location, orientation, and perspective of avirtual camera, and renders the map view to a device display. When instate 1905, the map view is static. With the application in state 1905,the user can perform numerous operations to modify the map view, searchfor entities (e.g., places of interest, addresses, etc.), retrieve aroute for navigation, etc.

In some embodiments, the integrated application is displayed on a devicewith an integrated touch-sensitive display. Various gesturalinteractions over the map may cause the application to perform differentmodifications to the map view (e.g., panning, rotating, zooming,modifying the map perspective, etc.). When the integrated applicationreceives gestural interactions over the map display (as opposed to touchinputs over various floating or non-floating controls overlaid on themap display), the application transitions to state 1910 to performgestural input recognition.

The gestural input recognition state 1910 differentiates betweendifferent types of gestural input and translates these types of inputinto different map view modification operations. In some embodiments,the mapping application receives the gestural input as translated by theoperating system of the device with the integrated touch-sensitivedisplay. The operating system translates the touch input into gesturetypes and locations (e.g., a “tap” at coordinates (x,y), a “pinch”operation with separate touch inputs at two different locations, etc.).At state 1910, the integrated mapping application of some embodimentstranslates these into the different map view modification operations.

When the application receives a first type of gestural input (e.g., twoseparate touch inputs moving together in a rotational motion over themap view), the application transitions to state 1915 to rotate the map.To rotate the map view, some embodiments modify the location and/ororientation of the virtual camera that determines which portion of themap is rendered to create the map view. When in 3D mode, for example,the mapping application rotates the virtual camera about a particularposition (e.g., the center of the touch inputs, the center of thedisplay, a location indicator identifying the user's location, etc.). Asthe first type of gestural input continues, the mapping applicationremains in state 1915 to continue rotating the map.

When the user releases the first type of gestural input, the applicationof some embodiments transitions to state 1930 to perform an inertiacalculation. In some embodiments, after the user releases certain typesof touch inputs, the application continues to perform the associated mapview modification for a particular amount of time and/or distance. Inthis case, after the user releases the rotation input, the applicationtransitions to the inertia calculation state 1930 to calculate theadditional rotation amount and the time over which this rotation shouldbe performed. In some embodiments, the application slows down therotation from the (angular) velocity at which the map was being rotated,as if a “frictional” force was applied to the map. As such, the inertiacalculation of some embodiments is based on the speed of the first typeof gestural input. From state 1930, the application transitions back tothe map modification state that the application was previously in. Thatis, when the application transitions from state 1915 (the rotationstate) to the inertia calculation state 1930, it then transitions backto state 1915 after performing the inertia calculation. After therotation of the map is complete, the application transitions back tostate 1905.

When the application receives a second type of gestural input (e.g., asingle touch input moving over the map view), the applicationtransitions to state 1920 to pan the map. To pan the map view, someembodiments modify the location of the virtual camera that determineswhich portion of the map is rendered to create the map view. This causesthe map to appear to slide in a direction derived from the direction ofthe second type of gestural input. In some embodiments, when the mapview is in a 3D perspective mode, the panning process involvesperforming a correlation of the location of the touch input to alocation on the flat map, in order to avoid sudden unwanted jumps in themap view. As the second type of gestural input continues, the mappingapplication remains in state 1920 to continue panning the map.

When the user releases the second type of gestural input, theapplication of some embodiments transitions to state 1930 to perform aninertia calculation. In some embodiments, after the user releasescertain types of touch inputs, the application continues to perform theassociated map view modification for a particular amount of time and/ordistance. In this case, after the user releases the panning input, theapplication transitions to the inertia calculation state 1930 tocalculate the additional amount to move the map view (i.e., move thevirtual camera) and the time over which this movement should beperformed. In some embodiments, the application slows down the panningmovement from the velocity at which the map was being panned, as if a“frictional” force was applied to the map. As such, the inertiacalculation of some embodiments is based on the speed of the second typeof gestural input. From state 1930, the application transitions back tothe map modification state that the application was previously in. Thatis, when the application transitions from state 1920 (the panning state)to the inertia calculation state 1930, it then transitions back to state1920 after performing the inertia calculation. After the panning of themap is complete, the application transitions back to state 1905.

When the application receives a third type of gestural input (e.g., twoseparate touch inputs moving closer together or farther apart), theapplication transitions to state 1925 to zoom in on or out of the map.To change the zoom level of the map view, some embodiments modify thelocation (i.e., height) of the virtual camera that determines whichportion of the map is rendered to create the map view. This causes themap view to include more (if zooming out) or less (if zooming in) of themap. In some embodiments, as the user zooms in or out, the applicationretrieves different map tiles (for different zoom levels) to generateand render the new map view. As the third type of gestural inputcontinues, the mapping application remains in state 1925 to continuezooming in on or out of the map.

When the user releases the second type of gestural input, theapplication of some embodiments transitions to state 1930 to perform aninertia calculation. In some embodiments, after the user releasescertain types of touch inputs, the application continues to perform theassociated map view modification for a particular amount of time and/ordistance (i.e., moving the virtual camera higher or lower). In thiscase, after the user releases the zoom input, the applicationtransitions to the inertia calculation state 1930 to calculate theadditional amount to zoom the map view (i.e., move the virtual camera)and the time over which this movement should be performed. In someembodiments, the application slows down the zooming movement from thevelocity at which the map was being zoomed in on or out of (i.e., thespeed at which the virtual camera changes height), as if a “frictional”force was applied to the camera. As such, the inertia calculation ofsome embodiments is based on the speed of the third type of gesturalinput. From state 1930, the application transitions back to the mapmodification state that the application was previously in. That is, whenthe application transitions from state 1925 (the zooming state) to theinertia calculation state 1930, it then transitions back to state 1925after performing the inertia calculation. After the zooming of the mapis complete, the application transitions back to state 1905.

For simplicity, the state diagram 1900 illustrates the map panning,zooming, and rotation processes using the same inertia calculationprocess (state 1930). However, in some embodiments, each of thesedifferent map modification processes actually uses a different inertiacalculation to identify the slow-down and stop for its particular typeof movement. In addition, some embodiments calculate and modify theinertia variables as the input is received rather than when the userremoves the gestural input.

When the application receives a fourth type of gestural input (e.g., twoseparate touch inputs moving up or down the touch-sensitive display inunison), the application transitions to state 1935 to modify theperspective view of the map. To change the perspective view of the map,some embodiments move the virtual camera along an arc over the map,modifying both the location and orientation of the virtual camera (asthe camera keeps the center of its field of view at a particularlocation on the map). In some embodiments, different zoom levels usedifferent arcs along which the virtual camera moves. Each of these arcshas a top point at which the virtual camera is pointing straight down,giving a 2D perspective view of the map. In addition, each arc has abottom point, that is the lowest point on the arc to which the virtualcamera can be moved. Thus, the fourth type of gestural input can causethe application to change between a 2D map view and a 3D perspective mapview in some embodiments. As the fourth type of gestural inputcontinues, the mapping application remains in state 1935 to continuemodifying the perspective view of the map.

When the user releases the fourth type of gestural input, theapplication of some embodiments transitions to state 1940 to perform aninertia calculation. In some embodiments, after the user releasescertain types of touch inputs, the application continues to perform theassociated map view modification for a particular amount of time and/ordistance (i.e., moving the virtual camera higher or lower). In thiscase, after the user releases the perspective view change input, theapplication transitions to the inertia calculation state 1940 tocalculate the additional amount to modify the perspective of the mapview (i.e., move the virtual camera along its arc) and the time overwhich this movement should be performed. In some embodiments, theapplication slows down the movement from the velocity at which the mapwas changing perspective (i.e., the speed at which the virtual cameramoves along its arc), as if a “frictional” force was applied to thecamera. As such, the inertia calculation of some embodiments is based onthe speed with which the fourth type of gestural input was performed.

In addition, for the perspective change operation, some embodimentstransition to a rebound calculation state 1945. As stated, theperspective change operation has a maximum and minimum perspective shiftallowed in some embodiments, which may depend on the zoom level of thecurrent map view. Thus, in addition to an inertia calculation, theapplication performs a rebound calculation at state 1945. The reboundcalculation uses the inertia calculation to determine whether themaximum point along the virtual camera arc will be reached and, if so,the velocity of the virtual camera at this point. Some embodiments allowthe virtual camera to move slightly past the maximum point to hit a“rebound” point, at which point the application turns the virtual cameraaround on its arc, moving it back towards the maximum point. Someembodiments include such a bounce-back functionality only on one end ofthe virtual camera arc (e.g., the bottom of the arc), while otherembodiments include the functionality on both ends of the arc. From therebound calculation state 1945, the application transitions back to theinertia calculation state 1940, then back to the perspective changingstate 1935 to display the map view movement. In addition, when the userperforms the fourth type of touch input for long enough and theperspective reaches its maximum point, the application transitionsdirectly from the state 1935 to state 1945 to calculate the reboundinformation and then transitions back to state 1935. After themodification to the perspective view of the map is complete, theapplication transitions back to state 1905.

The above states relate to the various multi-touch gestures over the mappresentation that the integrated mapping, search, and navigationapplication translates into different modifications to the mappresentation. Various other touch inputs can also cause the applicationto change states and perform various functions. For instance, someembodiments overlay a 3D selectable item on the map view (e.g., as afloating control), and selecting (e.g., with a tap input) the 3D itemcauses the application to transition to 1935 to modify the perspectiveof the map view. When the map view starts in a 3D perspective view, theapplication modifies the perspective into a 2D view; when the map viewstarts in the 2D view, the application modifies the perspective into a3D view. After the modification, the application returns to state 1905.

When a user is viewing a map in state 1905, the application presentsvarious labels as part of the map view. Some of these labels indicateplaces of interest, or other locations. When a user selects certainlabels (e.g., for certain businesses, parks, etc.), the applicationtransitions to state 1950 to display a banner for the selected location(e.g., an information display banner), then returns to the map browsingstate (with the banner displayed over the map). In some embodiments,this banner includes (1) a quick-route navigation UI control (e.g., abutton) that causes the application to retrieve a route (e.g., a drivingroute) from a current location of the device to the selected locationwithout leaving the map view and (2) an information UI control (e.g.,button) that causes the application to provide additional informationabout the location.

When a user selects the UI control button, the application transitionsfrom state 1905 to state 1955 to display a staging area for the selectedlocation. In some embodiments, this staging area displays a mediapresentation of the selected location (e.g., a 3D video presentation, aflyover view of the selected location, a series of images captured forthe location, etc.), as well as various information for the selectedlocation (contact information, reviews, etc.). The application stays inthe state 1955 as the user performs various operations to navigate thestaging area and view information within the staging area. When a userselects a UI control to transfer back to the map view, the applicationtransitions to state 1905.

From the map browsing view, the user can also easily access the searchfunction of the application. When a particular UI control (e.g., asearch bar) is selected, the application transitions to a search entrysuggestion state 1960. At the search entry state, some embodimentsdisplay a touchscreen keyboard with which the user can enter a searchterm. The search term may be a business name, an address, a type oflocation (e.g., coffee shops), etc. While the user enters characters,the application remains in state 1960 and provides suggestions based onrecent searches, the letters already entered, etc. Some embodiments mayuse prefix-based suggestions (e.g., suggestions starting with thecharacters already entered) as well as other suggestions (e.g., makingspelling corrections to add characters at the beginning of thealready-entered string, transpose characters, etc.). In someembodiments, the selections may also include recently entered routes inaddition to locations. If the user selects a cancellation UI control atthis stage, the application transfers back to state 1905 withoutperforming a search.

When the user selects a search term (either a suggested term or a termentered completely by the user), the application transitions to state1965 to display the search results over the map view, then transitionsto state 1905 with the search results displayed. Some embodimentsdisplay the search results as selectable items (e.g., pins) on the map;selection of one of the items causes a transition to state 1950 todisplay the banner for the selected item. In addition, the applicationof some embodiments automatically selects one of the search results(e.g., a “best” result) and displays this banner as part of the state1965.

As the application is a tightly integrated mapping, search, routing, andnavigation application, the user can easily access the routing functionfrom the map browsing state. When a particular UI control (e.g., a routeentry button) is selected, the application transitions to the routeentry state 1970. At the route entry state, some embodiments display atouchscreen keyboard with which the user can enter locations (e.g.,addresses, place names, place types, etc.) into both “to” and “from”fields in order to request a route. While the user enters characters,the application remains in state 1970 and provides suggestions based onrecent routes, recent searches, an autocomplete similar to thatdescribed for the search entry, etc. If the user selects a cancellationUI control at this stage, the application transfers back to state 1905without retrieving a route.

When the user selects a route (e.g., by entering a “to” location and a“from” location), the application transitions to the route displayingstate 1975. At this state, the application displays one or more routesfrom a first selected location to a second selected location over themap view (e.g., by overlaying route lines on the map view). Someembodiments automatically select a first one of the routes. The user canselect any of the other routes (e.g., by tapping over an unselectedroute), with the application remaining in state 1975 (but modifying thedisplay of the route lines to indicate the selection of the otherroute). In addition, when in state 1975, the application of someembodiments displays different UI controls related to routing andnavigation, including a direction list control, a navigation startcontrol, and others.

Also, various gestural interactions over the map on which the routes aredisplayed may cause the application to perform different modificationsto the map view (e.g., panning, rotating, zooming, modifying the mapperspective, etc.). When the integrated application receives gesturalinteraction over the map display while in the route display state 1975,the application transitions to state 1910 to perform gestural inputrecognition, with all of the gestural map modification operations (e.g.,corollaries to states 1915-1945) available. That is, the applicationtranslates the gestural input into panning, rotation, zoom, and/orperspective change operations similar to those described above forstates 1915-1945, with similar inertia and rebound features for thevirtual camera movement. Whereas the operations 1915-1945 return to themap browsing state 1905, the corollary operations accessed from theroute display state 1975 return to the route display state 1975.

In some embodiments, the route display state 1975 is accessible fromother states as well. For instance, if a user selects the quick-route UIcontrol on a banner while in state 1905, the application retrieves oneor more routes from the current location of the device to the locationwith which the banner is associated. In addition, some embodimentsdisplay previously requested routes among the search suggestions atstate 1960. When the user selects one of these suggested routes, theapplication transitions directly from state 1960 to state 1975 todisplay one or more routes over the map.

From the route display state 1975, the application can transition intovarious different modes depending on different controls selected by theuser. When the user selects a UI control to clear the routes, theapplication transitions back to state 1905 to display the map withoutany routes. In addition, the integrated application may enter one ormore navigation modalities from the route displaying state 1975.

When the selected route displayed at state 1975 starts at the currentlocation of the device and the user selects a navigation startingcontrol, the application transitions to the navigation state 1980. Insome embodiments, the application displays a cinematic transition fromthe map view into a more immersive 3D view for navigation. Within thenavigation state 1980 of some embodiments, a virtual camera follows thelocation of the user along the selected route in order to present theupcoming portions of the route. When either the route is completed (thedevice reaches the destination location) or the user selects a controlto end navigation, the application transitions to state 1905 to presentthe map browsing view 1905.

In some embodiments, various gestural interactions over the map on whichthe routes are displayed may cause the application to perform differentmodifications to the map view (e.g., panning, rotating, zooming,modifying the map perspective, etc.) while in the navigation mode 1980.In some embodiments, only some of the described map modificationoperations are available in the navigation mode. For instance, someembodiments allow the user to zoom in or out, but do not allow any othermodifications to the map. Thus, when the user provides gestural input,the gestural input recognition state 1910 filters out types of gesturalinput not associated with the zoom operation (and subsequently theapplication returns to state 1980). When the type of gestural inputassociated with the zoom operation is received, the gestural inputrecognition state recognizes this input and the application transitionsto a state similar to state 1925, for changing the zoom level of the map(with the inertia calculation, in some embodiments).

Other embodiments may enable different map modification operations. Forinstance, in some embodiments all of the gestural map modificationoperations (e.g., corollaries to states 1915-1945) are available whilein the navigation mode. Some embodiments allow a subset of the gesturalmap modification operations, such as zooming and a limited panningoperation. The panning operation of some embodiments, upon receiving thetype of gestural input associated with panning, moves the virtual camera(while in the navigation mode) to the side, then returns the virtualcamera back to pointing along the route. Whereas the operations1915-1945 return to the map browsing state 1905, the corollaryoperations accessed from the navigation state 1980 return to thenavigation state 1980.

When the selected route displayed at state 1975 starts at a locationother than the current location of the device (or the route is a walkingroute) and the user selects a navigation starting control, theapplication transitions to the stepping mode, or route inspection mode,at state 1985. In some embodiments, the application displays themaneuvers performed along the route one at a time (e.g., as navigationsigns). By providing gestural input (e.g., swipe gestures) to themaneuvers, the user can view the different maneuvers while in the routeinspection mode. The maneuvers are overlaid on a map and at least aportion of the route is displayed in the map.

As in the route display mode, various gestural interactions over the mapmay cause the application to perform different modifications to the mapview (e.g., panning, rotating, zooming, modifying the map perspective,etc.). When the integrated application receives gestural interactionover the map display while in the stepping mode 1985, the applicationtransitions to state 1910 to perform gestural input recognition, withall of the gestural map modification operations (e.g., corollaries tostates 1915-1945) available. That is, the application translates thegestural input into panning, rotation, zoom, and/or perspective changeoperations similar to those described above for states 1915-1945, withsimilar inertia and rebound features for the virtual camera movement.Whereas the operations 1915-1945 return to the map browsing state 1905,the corollary operations accessed from the stepping mode 1985 return tothe stepping mode 1985.

Furthermore, in some embodiments the gestural input recognitionrecognizes at least one type of gestural input over the displayedmaneuvers in order to switch between the maneuvers. When a particulartype of gestural input (e.g., a swipe gesture) is received over thedisplayed maneuver (as opposed to over the map view), the applicationtransitions to a state (not shown) for changing the displayed maneuver,then returns to state 1985.

When the integrated application receives gestural interaction over themap displayed while in the stepping state 1985, the applicationtransitions to state 1910 to perform gestural input recognition, withall of the gestural map modification operations (e.g., corollaries tostates 1915-1945) available. When the modification operations are done,the application returns to state 1985. When the user selects a controlto end stepping through the maneuvers, the application transitions tostate 1905 to present the map browsing view.

In addition, in some embodiments the application can transition from thestepping mode 1985 to an auto-stepping state 1990. When the user selectsa location tracking control while the application is in state 1985, theapplication transitions to an automatic stepping mode 1990, which is adifferent navigation modality. When in the automatic stepping mode ofsome embodiments, the integrated mapping, search, and navigationapplication displays the maneuver to which the device's location isclosest (e.g., as measured by a juncture at which the maneuver isperformed). When the device moves (e.g., along the route) to a locationcloser to a different maneuver, the auto-stepping mode automaticallydisplays the different maneuver. When the user deselects the locationtracking control, the application transitions back to the stepping mode1985. When the user selects a control to end navigation while in theauto-stepping state 1990, the application transitions to state 1905 topresent the map browsing view.

As in the stepping mode 1985, various gestural interactions over the mapmay cause the application to perform different modifications to the mapview (e.g., panning, rotating, zooming, modifying the map perspective,etc.). When the integrated application receives gestural interactionover the map display while in the auto-stepping mode 1990, theapplication transitions to state 1910 to perform gestural inputrecognition, with all of the gestural map modification operations (e.g.,corollaries to states 1915-1945) available. That is, the applicationtranslates the gestural input into panning, rotation, zoom, and/orperspective change operations similar to those described above forstates 1915-1945, with similar inertia and rebound features for thevirtual camera movement. Whereas the operations 1915-1945 return to themap browsing state 1905, the corollary operations accessed from theauto-stepping mode 1990 return to the auto-stepping mode 1990. Inaddition, some embodiments automatically turn the location trackingcontrol off when the user pans the map a particular distance, in whichcase the application returns to the stepping mode state 1985 rather thanauto-stepping state 1990.

II. Display of Navigation Signs

The above sections introduce the turn-by-turn navigation features ofsome embodiments. One such feature is the navigation signs provided bythe mapping application describing the different maneuvers for the userto perform. These signs may indicate turns, a distance over which tocontinue traveling straight, when to take a freeway off-ramp, or othermaneuvers for the user to perform. Some embodiments provide variousanimations for the signs, including showing the signs as passing overthe user location indicator in 3D mode, modifying the appearance of asign to indicate an upcoming maneuver, and using secondary signs whentwo maneuvers will be performed in rapid succession.

A. Realistic Look and Different Formats in Different Contexts

The navigation signs, in some embodiments, may have differentappearances in different contexts. Some of these differences aredescribed in greater detail further below. Specifically, graphicalindicators of maneuvers to perform (e.g., direction indicators that aredescribed further below) and instruction text describing those maneuversmay be adapted to fit the context of the navigation signs beingdisplayed. For example, different-sized signs may have either simple orcomplex maneuver descriptions, and instruction text may be adapted tothe size of the sign and may be based on other information displayedwithin the sign.

Some embodiments display the navigation signs in such a way as to givethe signs the appearance of a realistic road sign. Some embodimentsdisplay the navigation signs as rich, textured images (e.g., usingshadows, shading, etc.) as opposed to simply displaying a flat image onthe map display. In addition, some embodiments use shading for thenavigation sign that matches the color(s) of road signs in the areathrough which the application is navigating. The application also usesrealistic highway shields to mark roads in some embodiments. Forinstance, for numbered state and federal highways, the application willeither use the highway shield associated with the road within thenavigation sign (e.g., off to the side of the sign), replace the name ofthe road in navigation instructions with the highway shield, orotherwise include the highway shield in the graphical display.Generation and use of these road signs are further described in U.S.patent application Ser. No. 13/632,121, now published as U.S. PatentPublication number 2013/0322634, entitled “Context Aware VoiceGuidance.” U.S. patent application Ser. No. 13/632,121 is incorporatedherein by reference.

FIG. 20 illustrates several GUI scenarios in which such highway shieldsare used. The first such scenario 2005 illustrates the mappingapplication in turn-by-turn navigation mode, showing an instruction toproceed straight on US-101 North for 20 miles. In this example, the roadsign for US-101 is displayed inline within the text instruction “Gostraight on US-101 North”, as a substitute for the actual text “US-101”.Some embodiments replace text names of roads with road signs when theroad has a sign and that sign is available as an image to the mappingapplication.

The second example 2010 illustrates the highway shield displayed on theright side of the navigation sign rather than inline in the textinstruction. This scenario illustrates an alternative display used bysome embodiments for the same instruction as in example 2005. Thehighway shield in this case is displayed as the same size as thegraphical indicator arrow on the left side of the navigation sign. Inaddition, because the information is presented in the road sign, theapplication removes the “on 101 North” portion of the text that wouldotherwise be present.

The third example 2015 illustrates the case in which the navigation signis shaded to match the type of road shown in the highway shield. In thisscenario, the instruction tells the user to go straight on CA-1 North.The “CA-1” is replaced with the highway shield sign for CA-1. While someembodiments shade this sign using green (the color of signs used forCalifornia state highways), other embodiments shade the navigation signusing the color of the road shield signs found along the actual highway.Other embodiments use green to match the color of road instruction signsfound above freeways in the region in which the device is located (e.g.,green for California).

The fourth scenario 2020 illustrates a merge maneuver onto Interstate-5within the navigation sign. Much like the first example 2005, thisillustrates the road shield sign as inline text. Furthermore, shading isused within the road shield in order to match the look of the actualinterstate signs, with the top portion shaded red and the bottom portionshaded blue. As mentioned, some embodiments instead shade the entirenavigation sign using a combination of these colors.

Although FIG. 20 does not illustrate different appearances of directionindicators 2090, the mapping application of some embodiments usesdifferent appearances in order to adapt the direction indicators to fitthe context of the navigation signs being displayed.

1. Different Direction Indicators in Different Contexts

For a currently displayed navigation instruction sign, in the context offull-screen turn-by-turn navigation, the mapping application of someembodiments abstracts a maneuver down to two elements: a prominentstylized arrow roughly representing the path of the vehicle through thejuncture, and a de-emphasized set of lines and curves corresponding toother elements of the juncture. For instance, a right turn at aT-junction is represented by a large arrow with a right-angle joinedwith a smaller, dimmer segment that runs parallel to one of the largearrow's segments. The smaller segment will also be pushed off to theside so that the path taken by the vehicle through the juncturedominates the display. Such a representation of a maneuver whichincludes an arrow with junction context provides fairly completeinformation about the maneuver while remaining abstract and easilyunderstandable.

An alternate representation of a maneuver may omit the juncture contextentirely and simplify the primary arrow indicating the maneuver. When auser looks at maneuvers beyond the current maneuver (the next maneuverto make), the more detailed graphical representation may provide moreinformation than is required and be harder to read with a quick glance.For example, even if there is space to display the junction context fora secondary instruction that follows the current maneuver, someembodiments display only the simplified arrow for clarity. This adaptiveapproach also benefits space-constrained UI elements. While multitaskingor looking at lists of instructions, for example, the mappingapplication of some embodiments draws the simpler maneuver abstractionin order to produce something more easily discernible in a smaller area.

FIG. 21 illustrates several different scenarios in which the mappingapplication displays different types of graphical indicator arrows tovisually represent maneuvers to a user. The first scenario 2105illustrates route directions shown in a list view. The list viewdisplays a series of turn-by-turn instructions to get from a startlocation to an end location. In some embodiments, the user can view theturn-by-turn instructions without actually entering a navigation mode,or even following the route. In this situation, some embodiments displaya simple version of the graphical indicators for each turn. This is donefor space-saving reasons, as well as the fact that when the user is notactually approaching a maneuver, the intersection context is notespecially helpful.

The second scenario 2110 illustrates turn-by-turn navigation when theuser device on which the mapping application operates is locked. Asdescribed in detail below, the application is able to displayturn-by-turn navigation instructions even when the device is locked, inorder to continue providing instructions to the user. In this scenario,as shown, a simplified arrow is also displayed in some embodiments. Thisprovides a simple graphical indication of the turn within the lockscreen (in this case, a right turn), without providing the context datathat might be difficult for a user to pick out in the lock screen.

The third scenario 2115 also illustrates turn-by-turn navigation whenthe mapping application is not open (or not presently displayed) on thedevice on which the application operates. As described in detail above,the application displays turn-by-turn navigation instructions within thenotification banner space when the mapping application is not displayed.Much like in the lock-screen mode, the mapping application uses a simplegraphical indicator for the indicated maneuver (in this case a leftturn). Due to space constraints and the reasons described above for thelock-screen mode, the simple graphical indicator is used.

The previous three scenarios illustrate situations in which the simplegraphical indicators are used. One of ordinary skill in the art willrecognize that in some embodiments, the more complex stylized junctureplus maneuver graphical indicators might be used in the abovesituations. The following three scenarios illustrate indications inwhich these more complex indicators are used.

The fourth scenario 2120 illustrates route overview directions, in whichthe user can view an entire route from a starting location to endinglocation. The user can swipe through the different instructions (e.g.,using swipe gestures) to view the route segments between maneuvers.Here, the complex juncture indication is used, showing the intersectioncontext (a T intersection) and the maneuver made through theintersection, with the maneuver arrow emphasized over the intersectioncontext.

The fifth scenario 2125 illustrates navigation instructions in thecontext of the standard turn-by-turn navigation (i.e., not in thelock-screen mode, or with a different application open, etc.). In thiscase, the more complex arrow graphical indicator is used. In theillustrated example, the road juncture is slightly more complicated thanthe previous example, with a fourth branch angling up and to the rightfrom the direction of approach. The sixth scenario 2130 also illustratesnavigation instructions during turn-by-turn navigation. In this case,the maneuver being performed is a U-turn. Representing a U-turn with thejuncture branches as in scenario 2125 would result in the arrow pointingup and down the same branch (the bottom branch). As a result, theapplication instead displays a stored U-turn indicator arrow.

FIG. 22 illustrates several scenarios for the same turn, and how thedifferent arrows might be used for the same turn. The first scenario2205 shows a right turn onto 1^(st) St. in the turn-by-turn navigationinstructions. As in FIG. 21, the complex graphical indicator is used.The second scenario 2210 illustrates the situation during turn-by-turnnavigation in which the right turn onto 1^(st) St. is the second of twomaneuvers in quick succession. In this case, the second instructioncomes shortly after the first, so the application provides an indicationof the upcoming two maneuvers. The second maneuver is allotted lessspace on the display, and therefore the simplified arrow is used. Thethird scenario 2215 illustrates the use of the simplified arrowindicator in the route directions list. In addition, as shown for thesecond maneuver in the route directions list, some embodiments replacethe simplified directional indicator with a highway sign (shield) whenthe maneuver ends on a road for which such a shield/sign is available.The fourth and fifth scenarios 2220 and 2225 illustrate the simplifiedarrow indicators for the right turn in the lock-screen mode and when themapping application is not displayed on the device.

2. Different Navigation Instructions in Different Contexts

The mapping application of some embodiments displays textual routeinstructions in a large variety of cases, some of which are more spaceconstrained than others, and some in which other guidance elementsprovide information about a maneuver that can take the place of the textinstructions. Rather than selecting a single instruction string and thenshrinking the font or truncating as dictated by the constraints, theapplication uses a sophisticated method to synthesize strings that arebest adapted to each context from a number of details about the maneuveritself.

For a given context, the application chooses instruction text byconsidering factors such as the available space, the amount ofinformation conveyed by means other than text (e.g., the graphicalindicators, road signs, etc.), the localized length of each of theinstruction variants, among other factors. By synthesizing andevaluating several alternatives locally on the client device (as opposedto simply receiving instruction text from the mapping service), themapping application can pick an optimal instruction string in everyscenario. In addition, this approach allows for the application to usedifferent instruction text on a differently-sized device (e.g., usingmore text on a tablet computer as compared to a smaller smart phone). Asimilar approach can also be used for spoken instructions that need tofit within a particular amount of time, and when voice instructions areused, the application of some embodiments will reduce the length of thedisplayed instructions.

FIG. 23 illustrates an example of the synthesis of differentinstructions for a particular maneuver at a juncture according to someembodiments. FIGS. 24 and 25 then illustrate different scenarios inwhich these different instructions for the maneuver are used. As shown,the mapping application uses received route instructions and juncturedata to identify specific aspects of maneuver instructions. The table2305 conceptually illustrates how various strings might be generated fora juncture. Specifically, the maneuver instructions include an “At”field, a “Turn” field, an “Onto” field, a “Towards” field, and a “For”field. For each juncture, the application initially populates thesestring fields, in order to synthesize the instructions from the fields.

In some embodiments, the “At” field is based on map information thatincludes traffic light and stop sign information, etc. For the examplesshown in FIG. 23, the first juncture takes place “at the end of theroad”, while the second juncture takes place “at the next light”. The“Turn” field describes the maneuver to be made; examples of this fieldinclude “turn right” (the maneuver performed at the first juncture),“exit freeway”, “keep left”, “slight left turn”, “U-turn”, or othermaneuvers. The route directions that include a maneuver description maybe mapped to different possible strings for the “Turn” field.

The “Onto” field indicates the pathway (i.e., street, freeway, etc.)onto which the maneuver exits the juncture. In the case of the firstjuncture in FIG. 23, the maneuver exits the juncture “onto 1^(st) St.”.The “Towards” field indicates a marker (taken from the map data orjuncture data) towards which the exit branch points. In someembodiments, the mapping application analyzes the exit branch of thesubsequent juncture, and uses the name of this road as the “towards”field. In the example, the second juncture is a left turn onto B St., sothe “Towards” field for the first juncture indicates that the maneuverexits “towards B St.” Other embodiments use either the next road withwhich the exit street of the present junction intersects, a major road(e.g., a freeway), or other easily recognizable descriptor (e.g., acity, etc.). The “For” field indicates the distance along which theroute will follow the road in the “Onto” field (that is, the road ontowhich the juncture exits). Thus, in the example instructions, the nextjuncture will be in 0.1 miles, so the “For” field is “for 0.1 miles”.

Next, after generating each of the component strings for a set ofinstructions, the mapping application of some embodiments generatesdifferent levels of instructions. The table 2300 illustrates a set ofsynthesized instructions for the first juncture. Specifically, the table2300 illustrates five sets of instructions, of varying lengths, for aparticular juncture. However, one of ordinary skill in the art willrecognize that different embodiments might include fewer, additional, ordifferent synthesized strings based on the set of string fields.

The first instruction set uses all five of the fields. This is thelongest instruction set, reading “At the end of the road, turn rightonto 1^(st) St., towards B. St. for 0.1 miles”. As it is the longestinstruction set, the application assigns the instruction set a rankof 1. The second instruction set removes the “For” field, using only the“At”, “Turn”, “Onto”, and “Towards” fields. The third instruction setremoves the “At” field. These fields add context, and are therefore niceto have when additional room is available. However, they are lessintegral to the maneuver itself, and therefore are the first fields toremove when shortening the instruction text. Next, for the fourthinstruction set, the application removes the “Towards” field, as the“Turn” and “Onto” fields are considered more important. Lastly, thefifth instruction set contains only the “Turn” field, simply stating“Turn right”.

Again, some embodiments will include additional instruction sets, whendifferent length instructions (that still make sense) are available. Forinstance, some embodiments will include an instruction set that removesthe “At” field but keeps the “For” field, in the case that the “For”field is shorter than the “At” field. This enables the application tohave another option in case the second instruction set (with the “For”field removed) is just slightly too long for the allocated space.Furthermore, some embodiments may include additional, fewer, ordifferent fields. For instance, some embodiments might include a “In”field, that gives the distance to the upcoming juncture (i.e., “In 0.5miles, . . . ”).

FIGS. 24 and 25 illustrate several different scenarios in which themapping application displays different examples of the adaptiveinstructions for the particular maneuver of the first juncture in table2305 in a variety of different situations. In this case, the fullinstructions are “In 0.5 miles, at the end of the road, turn right onto1^(st) St. towards B. St. for 0.1 miles.” However, as the example doesnot include an “In” field, the highest ranked instructions are slightlyshorter than this. In order to determine which instruction set to usefor a particular display, the mapping application of some embodimentsdetermines a maximum length for the instruction set, then chooses thehighest ranked set that fits into the allotted space.

The first scenario 2405 illustrates instructions for the particularmaneuver displayed during turn-by-turn navigation. In this case, theapplication allots three text lines for the instruction. The distance(0.5 miles) is already displayed in large font at the top of thenavigation sign, but this is not counted as one of the text lines. Withthree lines available, the highest ranked instruction set can be used inthe navigation sign.

The second scenario 2410 illustrates turn-by-turn navigationinstructions for the particular maneuver while in lock screen mode. Inthis mode, only two lines of large text are allotted in someembodiments, so the highest ranked instructions that fit use only the“Turn” and “Onto” fields. This simplifies into the direction of the turnand the street onto which the user turns. The third scenario 2415illustrates navigation instructions for the maneuver while the mappingapplication is not open on the device, in which case the instructionsshow up as an alert banner. In this case, the application only allotsone line to the instructions, so the lowest ranked instructions (“Turnright”) are used.

The fourth scenario 2420 illustrates the display of information in thelist view for route directions. This view, as described above, listssubsequent instructions for each of the maneuvers along a route. In someembodiments, the banners in the list view for each direction are of avariable height, and therefore the full instruction set is always used.Thus, the highest ranked set of instructions, “At the end of the road,turn right onto 1^(st) St. towards B. St.” is used for the firstmaneuver in the list. As shown, this maneuver takes an extra line oftext as compared to the next two maneuvers.

The fifth scenario 2425 illustrates turn-by-turn navigation in 3D mode.As compared to the first scenario 2405, some embodiments allot less roomin the navigation sign for the instruction set when in 3D mode, in orderfor more of the 3D display to be viewable. As such, the application usesthe third ranked instruction set, because this is the largestinstruction that fits in the two lines using the given text size.

FIG. 25 illustrates additional scenarios in which the mappingapplication uses the synthesized instruction sets. The sixth scenario2505 illustrates the display of route overview instructions that theuser can step through (e.g., with sweep gestures). In some embodiments,the application allots the same amount of space for step-throughinstructions as for turn-by-turn navigation, and therefore theapplication again uses the highest ranked instruction set that includesall of the fields.

The seventh scenario 2510 is the same as the first scenario 2405, butexplicitly indicates that the spoken navigation is turned off. This isprovided here to contrast with the eighth scenario 2515, in which voiceinstructions are enabled during turn-by-turn navigation. For voicenavigation, the application determines a maximum amount of time allowedfor speaking the instructions, then determines the highest ranked set ofinstructions that can be spoken within this allotted time. In this case,the time allows the entirety of the highest ranked instruction set to beselected. In addition, when voice navigation is activated, theapplication reduces the size of the displayed navigation sign. As such,the application displays the third ranked instruction set within thedisplay.

Finally, the mapping application of some embodiments may operate ondifferent types of devices with different size display screens. Forexample, the application might operate on both smart phones and largertablet computers. When operating on a larger device, some embodimentsallow more room for the navigation sign. The ninth scenario 2520illustrates turn-by-turn 3D navigation on a larger device (a tabletcomputer). Unlike in the fifth scenario 2425, the navigation signprovides enough room for the highest ranked instruction set to be used.

The above description describes some embodiments that generate severaldifferent instruction sets for a maneuver, rank the instruction sets,and then adaptively determine which of these instruction sets best fitsinto a particular space. In some embodiments, the application identifiesa maximum number of characters available to use for the instructiondisplay. The application then starts with the highest ranked instructionset and determines whether the instruction set fits into the identifiednumber of characters. When the instruction set fits, the applicationselects and displays the instruction set. When the instruction set doesnot fit, the application moves to the next ranked instruction set andperforms the same test. If none of the instruction sets fit, then theapplication uses the one that comes closest to fitting. Some embodimentsthen truncate the instruction set with an ellipsis to indicate that theinstruction set does not completely fit within the space. This mayresult in elements being removed from the string.

In addition to text, some embodiments use text substitutes within theinstruction sets. Specifically, for roads represented by shield signs(e.g., interstate freeways, state routes), the application uses theshield representation of the road rather than the road name (e.g., ablue and red shield with “I-5” inside of it instead of “Golden StateFreeway” or “Interstate 5”. Some embodiments treat these signs as afixed number of characters when assessing the different instructionsets.

The above description describes some embodiments of the mappingapplication in which the decision regarding which elements to use isperformed primarily based on trying to use the maximum lengthinstruction set. Some other embodiments factor in whether certainelements of an instruction set are presented to the user in a differentvisual manner, and may potentially remove these elements.

For instance, when displaying a detailed instructional arrow that makesclear a turn is a slight right turn, some embodiments shorten theinstruction to remove the “slight” or even remove the entire referenceto the turn, instead using instructions along the line of “CA-17 Stowards Santa Cruz”. Similarly, if displaying a large road shield sign,then the “CA-17 S” portion of the instruction might be omitted.

B. Dynamic and Animated Presentation of Signs

The above-described situations of FIG. 20 illustrate static display ofthe navigation signs (i.e., not showing any changes made to the signs).Some embodiments provide animation or other dynamic displays of thesenavigation signs. These displays include displaying the appearance ofthe sign passing over the head of the user representation (thenavigation puck) in the map display as a user makes a maneuver and thesign is removed. In addition, subtle animation may be applied to a signas a maneuver approaches in order to bring the upcoming maneuver to theuser's attention. Finally, when two maneuvers occur in short succession,the application displays the navigation sign for the second maneuver asqueued up behind the first sign.

1. Animated Removal and Presentation of Navigation Sign

FIG. 26 illustrates, over four stages 2605-2620, the animation of someembodiments for removing a navigation sign and introducing the nextsign. In some embodiments, the animation of the removed sign mimics thatof a road sign passing overhead on a highway. While this figureillustrates the animation within the context of 3D mode, someembodiments also include the animation in 2D mode. Other embodimentsspecifically provide the animation for 3D mode.

The first stage 2605 illustrates a navigation sign 2625 indicating amaneuver of merging onto Main St. for the user to perform in 100 ft. Thesecond stage 2610 illustrates the animation to remove the navigationsign 2625 as the user performs the maneuver. As the user physicallymerges onto Main St., the navigation sign 2625 enlarges and beginsdisappearing from the field of view, as would a road sign above afreeway. In some embodiments, the mapping application also applies aperspective tilt to the sign, to further mimic the appearance of thesign passing overhead.

At the third stage 2615, the subsequent navigation sign 2630 begins toappear from the horizon, or a closer approximation of the horizon. Someembodiments do not actually render the map all the way out to thehorizon in 3D mode, and start animating the upcoming navigation signfrom the distance at which the 3D rendering ends. This animation ismeant to resemble the approach towards a road sign on the freeway,though often at a faster speed (in order to quickly bring the navigationsign to full size, and avoid the distraction of a lengthy animation).The fourth stage 2620 illustrates the resultant display, with thesubsequent navigation sign 2630 displayed at the top of the screen inthe normal position.

In addition to the animations shown in FIG. 26, some embodiments alsoinclude more complex animations in some cases. As one example, someembodiments rotate a navigation sign as it leaves the display when auser makes a turning maneuver, in order to mimic the appearance of auser turning underneath the sign.

2. Occasional Emphasis

In some cases, the mapping application may display a navigation signwell before the maneuver described by the navigation sign will beperformed. For instance, if a user enters a freeway, and the nextmaneuver involves a freeway exit in 15 miles, the application maydisplay a navigation sign indicating the upcoming freeway exit wellbefore the user needs to begin preparing to actually exit the freeway.When it comes time to alert the user that the juncture at which toperform the maneuver is approaching, different embodiments use differenttechniques. Some embodiments include audio alerts, with the user deviceproviding voice navigation to indicate that the juncture is approaching.

Some embodiments, either in conjunction with the audio alert or wheneverthe audio alert is turned off, provide a visual indication that themaneuver is upcoming through the display of the sign. For instance, insome embodiments the application modifies the color of the sign (e.g.,from green to white or green to yellow) along with the color of thegraphical indicator arrow (e.g., from white to black). Other embodimentsdisplay a less obtrusive shimmer over the navigation sign, intended tocatch the user's attention without being overly obtrusive.

FIG. 27 illustrates such a shimmer animation over four stages 2705-2720.These stages illustrate the background of the display as gray, in orderto contrast with the shimmer as it moves across the sign (shown inwhite). The first stage 2705 illustrates a navigation sign 2725,currently indicating a right turn maneuver in 1000 ft.

At the second stage 2710, the right turn is now only 500 ft. away. Theapplication has judged that this is the appropriate distance at which toalert the user to the upcoming maneuver, and therefore has begundisplaying a shimmer across the navigation sign 2725. The third andfourth stages 2715 and 2720 illustrate the continuation of thisanimation. In some embodiments, the animation resembles a light beingmoved across the sign from left to right. Other embodiments display asimilar animation from right to left, or other such animations (e.g., alight radiating out from the center of the sign, etc.).

Some embodiments vary the distance from the maneuver at which theanimation begins based on various factors, such as the speed at whichthe device is moving (based on location tracking information) and thespeed limit of the road on which the user is currently traveling. Forexample, some embodiments have a set time before the intersection thatthe animation should be displayed, and use this speed information tocalculate the appropriate distance. Some embodiments also vary thedistance based on the type of maneuver being made (e.g., allowing moretime for exiting a freeway than for making a right turn off of aone-lane road).

3. Secondary Signs

When a route requires two distinct maneuvers in rapid succession, someembodiments display the navigation sign for the second maneuver asstacked underneath the navigation sign for the first maneuver. Thisalerts the user to the impending nature of the second maneuver. Whenseveral maneuvers will be performed in succession, some embodimentsstack more than two navigation signs on top of each other.

FIG. 28 illustrates the display of two signs for maneuvers in quicksuccession over four stages 2805-2820. In the first stage 2805, a firstnavigation sign 2825 indicates that the upcoming maneuver, at a distanceof 1000 ft., is a left turn onto East St. As this is a full sizeturn-by-turn navigation sign, the application displays a first type ofgraphical indicator arrow (i.e., a complex arrow) for this maneuver. Ascan be seen on the map with more careful review than may be available toa driver (who will mostly be looking at the road), a right turn ontoSouth St. will be required shortly after the left turn onto East St. inorder to follow the given route. In order to make this more apparent tothe user, the application displays a second navigation sign 2830underneath the first navigation sign 2825. The second sign includes asecond type of graphical indicator arrow (i.e., a simpler arrow) as lessspace is provided. Furthermore, less information is provided to the userin the second sign 2830.

The second stage 2810 illustrates that the user has now traveled 900feet, so that there are only 100 ft. from the left turn maneuver. Otherthan the updates to the distance in the navigation sign 2825 (and themovement of the 3D map), the display has not yet changed. The thirdstage 2815 illustrates the display immediately after the left turnmaneuver has been performed onto East St. As shown, the secondnavigation sign 2830 is now a full-sized navigation sign with a complexgraphical indicator arrow and additional textual information (a distanceof 50 feet and text instructions to turn right). Some embodimentsanimate the transition from the smaller sign to the full-size sign,while other embodiments simply replace one with the other.

The fourth stage 2820 illustrates the display after the user has madethe second maneuver (the right turn onto South St.). The application nowdisplays a navigation sign 2835 for the next maneuver, a left turn ontoWest St. Because this maneuver is 2.8 miles away, the application didnot stack sign 2835 under sign 2830. Because the navigation is in 3Dmode, some embodiments do display the animation described above byreference to FIG. 26.

In the above example, the application stacks signs for maneuvers thatoccur 50 feet apart, but does not stack signs for maneuvers that occurseveral maneuvers apart. The threshold distance for when to consider twomaneuvers subsequent may depend on a variety of factors. Someembodiments store a set distance that is not variable. Other embodimentslook at the type of roads involved in the maneuver (e.g., based on afunctional road class variable that describes the road in back-end mapdata) or the speed limits, assume a likely speed for the user after themaneuver, and set the threshold distance based on this data (i.e., basedon a threshold time between maneuvers, such as 30 seconds).

III. Navigation Instructions when not in Navigation Application

A. Instructions when Device is Unlocked and Navigation is Operating inBackground

Some embodiments allow the navigation application to run in thebackground while other applications are running in the foreground. Theseembodiments provide unobtrusive navigation instructions in theforeground even while the main navigation application is running in thebackground and another application or an application launcher is runningin the foreground. Examples of applications running in the foregroundinclude voice-activated personal assistant, mail, browser, phone,calendar, or any other application available on the device.

The navigation application of some embodiments provides a navigation bar(sometimes called a “banner” or “navigation banner”) as well as aregular status bar on the screen. Some embodiments provide a navigationstatus bar when no navigation instructions are being provided andprovide a navigation instruction bar when navigation instructions arebeing given. FIG. 29 illustrates a user device display 2900 whennavigation is in operating in background in some embodiments of theinvention. The user device display 2900 is shown in four stages2901-2904.

In stage 2901, the display 2900 shows navigation application 2905, astatus bar 2980, and a button 2915. The status bar 2980 shows differentinformation such as battery level, time, reception bars, etc. In someembodiments, the status bar displays an indicator such as an arrow,which indicates that the navigation application or a map application isrunning. In this stage 2901, the navigation application 2905 is runningin the foreground until the device receives a selection (e.g., a click)on button 2915 that switches from the navigation application to theapplication launch view, which can itself be characterized as anapplication launching application. In some embodiments, there are othercontrols instead of or in addition to the button that switch thenavigation application to another application (e.g., the applicationlaunch view or other applications). The stage 2901 also shows that theroad names are displayed on road signs and not in banners. As mentionedabove, the mapping application of some embodiments may display the roadnames on the road and/or in the banners regardless of the mode in whichthe mapping application operates.

In stage 2902 application launcher 2975 is displayed in the foreground.The foreground application launcher 2975 has icons 2925 that have theirnormal functions (e.g., launching other applications) while thenavigation application runs in the background. In stage 2902 abackground navigation status bar 2910 is shown below the status bar2980. Some embodiments display the status bar 2980 and/or the navigationstatus bar 2910 in a different color (e.g., green) when navigation isrunning in background (as shown in stage 2902) than the status bar color(e.g., gray) when navigation is not running in background (as shown instage 2901). In other embodiments, the status bar 2980 is the same colorwhen the navigation application is running in the background, thenavigation application is off, or the navigation application is runningin the foreground. In some embodiments, the thickness of the navigationstatus bar is the same or approximately the same (e.g., 75% to 125% ofthe thickness) as the thickness of the status bar when the navigationapplication is not currently displaying a direction in a navigationinstruction bar.

The navigation status bar 2910 in some embodiments is both an indicatorthat the navigation application is running in the background and acontrol for bringing the navigation application to the foreground. Thenavigation status bar 2910 in some embodiments is not limited to beingdisplayed only with the application launching screen 2975, but rather isdisplayed below the status bar 2980 at the top of any application thatis running in the foreground.

In stage 2903, the navigation status bar 2910 is selected by touchingthe navigation status bar 2910 on the screen. Some embodiments alsoallow the selection of the navigation bar by other touch-based ormotion-based input devices as well as non-touch based or motion-basedinput devices. Some devices used for selection in some embodimentsinclude keyboards, mice, joysticks, touch-pads, and the like (e.g.,selection can be by a click from a mouse). The selection of thenavigation status bar 2910 (as shown in stage 2903) causes thenavigation application 2905 to return to the foreground in stage 2904.In addition to utilizing navigation status bar 2910 to return to thenavigation application (i.e., to bring the navigation application toforeground), in some embodiments the navigation bar has other functions.For instance, the navigation status bar 2910 is used in some embodimentsto provide navigation instructions (e.g., turn-by-turn directions) whilethe navigation application itself is still in the background. In otherembodiments, the navigation status bar is replaced at various times by anavigation instruction bar that provides instructions.

FIG. 30 conceptually illustrates a process 3000 of some embodiments forproviding directions while a navigation application is running in thebackground. FIG. 30 will be described with respect to FIG. 31, which isbriefly described first. FIG. 31 illustrates a user interface of someembodiments in which navigation instructions are given while thenavigation application is running in the background and anotherapplication is running in the foreground. The figure shows six stages3101-3106. The first stage includes status bar 3180, navigation statusbar 3110, and foreground application 3115. The remaining stages3102-3106 show the changes to the navigation status bar 3110 (e.g., itsreplacement by navigation instruction bars 3120-3150) as the device ismoved toward, and then passes a navigation point (sometimes referred toherein as a maneuver, some navigation points represent junctions in theroad).

As shown in FIG. 30, process 3000 displays (at 3005) the navigationapplication in the foreground. The process then determines (at 3010)whether the control (e.g., button 2915 of FIG. 29) has been activated.If not, the process keeps displaying the navigation application in theforeground until the control is activated (or in some embodiments, untilsome other control is activated or the device goes into a sleep mode).When the control is activated, the process displays (at 3015) theapplication launching mode in the foreground and displays (also at 3015)the navigation status bar 3110 to indicate that navigation is running inthe background. This is illustrated in stage 3101 in FIG. 31.

One of ordinary skill in the art will understand that in someembodiments, a navigation bar (a navigation instruction bar and/or anavigation status bar) appears at the top of some or all foregroundapplications, not just the application launching application. Theactivation of one or more controls in some embodiments causesapplications other than the launching application to move to theforeground. Furthermore, in some embodiments the navigation barcontinues to appear above foreground applications after switchingbetween one foreground application and another, and not just whenswitching directly from the navigation application to a particularforeground application. An example of a navigation bar being displayedabove another application is shown in FIG. 32, described below.

Process 3000 then determines (at 3020) whether the user device is near anavigation point (e.g., at a waypoint turn). While the applicationdetermines (at 3020) that the device is not near a navigation point thedisplay remains as shown in stage 3101 of FIG. 31.

Stage 3101 shows the state of a device when the navigation applicationis active as a background application and the foreground application3115 is the application launching screen. The navigation application hasnot been turned off, but instead has been left on in the background. Thevisible indication in stage 3101 of the navigation application being onin the background is the navigation status bar 3110. Also, someembodiments display the status bar 3180 in a different color from itsusual color when navigation is running in the background. In someembodiments the status bar 3180 and the navigation status bar 3110 areshown in various shades of green. In some embodiments, the colors orshades of one or both of the status bar and the navigation bar changeover time to draw attention to the fact that the navigation applicationis executing in the background.

At this stage 3101, the device (and the person or vehicle carrying thedevice) is far from the next navigation point. The application of someembodiments, including the one illustrated in FIG. 31 do not displayturning information for the entire span of time that the application isrunning in the background. In some such embodiments, when the device isnot near a navigation point (e.g., when no turn is imminent) the devicedisplays, in the navigation status bar 3110, “touch to view navigation”,or “touch to return to navigation” or some other message indicating thatselecting the navigation bar will bring the navigation application tothe foreground. In other embodiments, the navigation instructions aredisplayed whether or not the device is near a navigation point.

Referring back to FIG. 30, when process 3000 determines (at 3020) thatthe device is approaching the next navigation point, the process changes(at 3025) the navigation status bar 3110 to a navigation instruction bar3120 to display the new navigation instruction. This is shown in stage3102 of FIG. 31. In stage 3102, the device is approaching a navigationpoint (a left turn in 500 feet). In this stage 3102, the navigationinstruction bar 3120 displays navigation instructions, which include anarrow indicating a left turn and a distance (500 feet) to the left turn.Process 3000 then displays (at 3030) a countdown (in feet) until itdetermines (at 3035) that the navigation point has been passed.

In some embodiments, the navigation bars in stage 3101 and 3102 aretreated as separate entities that happen to occupy a similar place onthe screen. In such embodiments the navigation bar of stage 3101 can becharacterized as a “navigation status bar”, while the navigation barwith navigation instructions in stage 3102 can be characterized as a“navigation instruction bar” or a “navigation direction bar”. In someembodiments, the navigation instruction bar 3120 is thicker than thenavigation status bar 3110 (e.g., twice the thickness or more) andcovers up the status bar. In other embodiments, the navigation bar istreated as a single entity that expands (e.g., to twice its previousthickness or more) to cover or replace the status bar when thenavigation bar displays navigation directions.

In stages 3103 and 3104, as the device moves closer to the navigationpoint, the distance to the navigation point is counted down in thenavigation instructions in navigation instruction bars 3130 (100 feet)and 3140 (0 feet). In stage 3104, the instructions have begun to switchto the next instruction.

In stage 3104, the actual turn is taking place. The navigationinstructions in navigation instruction bar 3150 (shown in stage 3105)are replacing the previous navigation point instructions in navigationinstruction bar 3140 with the instructions for the next navigationpoint. In some embodiments, including the illustrated embodiment, thenavigation instructions are switched in a simulation of a flipping signwith multiple faces. Accordingly, instruction 3140 shows the instruction“0 feet turn left” as it begins to flip. In some embodiments, the signflips up, in some embodiments the sign flips down. In other embodiments,the device uses other transition methods to remove the old navigationinstruction in navigation instruction bar 3140 and replace it with thenew navigation instruction in navigation instruction bar 3150 (in stage3105). For instance, some embodiments simulate a new instruction slidingup, down, or sideways while the old instruction slides in the samedirection. Other embodiments simulate sliding the new instruction overthe old instruction. Still other embodiments simply have the oldinstruction disappear to be replaced by the new instruction.

When a navigation point is reached, process 3000 determines (at 3040)whether the final destination has been reached. If the final destinationhas been reached, the navigation ends (this is illustrated in FIG. 33,described below). If the final destination has not been reached thenthere is a new navigation point to display (at 3045). This is shown instage 3105 of FIG. 31.

Stage 3105 occurs just after the left turn has been completed. Thenavigation instruction in navigation instruction bar 3150 has fullyreplaced the navigation instruction in navigation instruction bar 3140.The new navigation instruction in navigation instruction bar 3150indicates a significant distance to the next navigation point. Asmentioned above, the applications of some devices are programmed todisplay navigation instructions primarily when the device is near anavigation point, not at all times. Accordingly, after displaying thenext navigation instruction in navigation instruction bar 3150 for apre-set period (or in some embodiments after a preset distancetraveled), the application in some embodiments returns to showingnavigation status bar 3110 in stage 3106 (and process 3000 returns tooperation 3015). However, when the new navigation point is determined(at 3050 of FIG. 30) to be near, the process 3000 immediately beginscounting (at 3030) down the distance to the next navigation point.Different applications of different embodiments use various differentdistances to determine whether to show the navigation status bar 3110 ornavigation instructions (e.g., instructions in navigation instructionbar 3120). In some embodiments, the applications switch on theinstructions at 1 mile, or half a mile, or a quarter mile, or 1000 feet,or 750 feet, or 500 feet, or 250 feet, or some other distance.

FIG. 32 illustrates a navigation bar displayed at the top of anapplication. The figure demonstrates that the navigation bar isdisplayed in applications other than the application launchingapplication. The figure is shown in stages 3201-3203. In stage 3201, thenavigation application is in the foreground and the user has entered acommand (e.g., double pushing a button 3210) to bring up a list ofapplications currently running in the background. In stage 3202, thedevice is displaying a set of icons 3220 representing applicationscurrently in the background. In some embodiments, the set of icons 3220pushes up the UI of the application in the foreground as shown. In otherembodiments, the UI of the application in the foreground gets overlaidwith the set of icons 3220 instead of being pushed up.

The second stage 3202 also shows that the user selects icon 3225commanding that the application represented by icon 3225 (e.g., a webbrowser) be moved to the foreground and the navigation application bemoved to the background. One of ordinary skill in the art willunderstand that this is just one of many ways that some embodimentsswitch the navigation application into the background and anotherapplication into the foreground. For example the user could switch tothe application launching view and launch an application, which wouldthen replace the application launching view as the foregroundapplication.

The web browser 3230 that the device switches to the foreground is shownin stage 3203. At the top of the screen is a navigation instruction bar3235 indicating that the navigation application is running in thebackground and directing the user to turn right in 50 feet. In someembodiments, the status bar and a navigation status bar (e.g., as shownin FIG. 29) will appear when the navigation application is not currentlyproviding a direction.

After following the navigation instructions shown by the device, theuser will reach his intended destination. FIG. 33 illustrates the userinterface of a device 3300 in some embodiments where the device reachesits destination while the navigation application is running in thebackground of another application. The figure shows three stages3301-3303. The first stage 3301 shows navigation instruction bar 3310,and foreground application 3340. As shown, the instructions innavigation instruction bar 3310 indicate “50 Feet Go Straight”.

Stage 3302 illustrates the user device 3300 when the destination isapproached. As shown in this stage, the navigation instruction bar 3310indicates “Destination on the Left”. Stage 3303 illustrates the userdevice 3300 after the destination is reached. As shown, navigationinstruction bar 3310 of stages 3301 and 3302 is removed from the screento indicate that the navigation instructions are finished and status bar3380 returns to the screen. In some embodiments, the navigationapplication remains on in the background, but not visibly displayed atthis stage 3303. In other embodiments the navigation applicationswitches itself off at this stage 3303. In still other embodiments, thedevice continues to display the navigation bar after the destination isreached. Furthermore, the navigation application of some embodimentsidentifies a location as the end of vehicular navigation and indicatesthat the rest of the journey must be completed on foot, which thenavigation application directs (e.g., in the navigation instructionbar).

The stage 3303 also shows that the icons 3390 have not moved. However,in other embodiments, the icons 3390 may move up to occupy at least aportion of the space that used to be occupied by the navigationinstruction bar 3310 at the previous stages in some embodiments, whenthe navigation instruction bar is removed from the screen.

As described above, the navigation status bar and the navigationinstruction bar are treated as distinct components in some embodiments.The above described figures show the navigation status bar below astatus bar. However, when the navigation application is running in thebackground, the status bar itself is replaced with a navigation bannerin some embodiments. This navigation banner is twice the height of theregular status bar in some embodiments. The navigation banner of someembodiments displays some or all of the same information as the statusbar it replaces. In some embodiments, the navigation banner displaysthat information when the device is not nearing a navigation point anddoes not display it when the device is nearing a navigation point. Whenthe device is nearing a navigation point, some or all of the statusinformation is removed so that a direction relevant to the upcomingnavigation point can be seen more clearly.

Devices that execute navigation applications of some embodiments includetelephonic devices. In some embodiments, when a telephone call is beingprocessed by the device, and the navigation application is running inthe background, data about the telephone call (e.g., call time) replacesa navigation status bar or the instruction bar with a telephone callstatus bar.

FIG. 34 illustrates interaction between a call status bar and anavigation instruction bar. The figure is shown in three stages3401-3403. In stage 3401, a call is going on while the device isdisplaying an application launching view. The call is indicated by acall status bar 3415 under the status bar 3410. The call status bar insome embodiments indicates that a call is ongoing, contains an indicatorof the duration of the call, and allows the user to select the callstatus bar to return to a screen view normally used for handling calls.In some embodiments, the original status bar 3410 (showing battery lifeetc.) turns to a color that indicates that a call is ongoing (e.g., redor green). In some embodiments, the telephone call status bar 3415 is asimilar color to a color that the original status bar displays duringthe call (e.g., both are shades of red or both are shades of green).

In some embodiments, the navigation instruction bar 3420 re-emerges andreplaces the phone data under some circumstances. In stage 3402, thedevice is near a navigation point. Therefore, the navigation instructionbar 3420 replaces the call status bar 3415 and the status bar 3410.After the navigation point is passed, the call status bar 3415 and thestatus bar 3410 are redisplayed as shown in stage 3403. In theillustrated embodiment of FIG. 34, the call status bar is redisplayed assoon as the navigation point is passed. However, in some embodiments,the phone call status bar is not redisplayed until after the nextnavigation instruction is displayed in the navigation instruction bar3420.

The stages 3302 and 3303 show that the icons 3390 have not moved.However, in other embodiments, the icons may move up or down to occupydifferent spaces depending on the presence of the call status bar 3415and the navigation instruction bar 3420.

B. Instructions when Device is Locked

1. Layout

In some embodiments, devices with multiple functions (e.g., mobilephones that run multiple applications) can be placed into locked modefrom various applications. In some embodiments, there are multiple waysto place a device into locked mode. The locked mode of some embodimentsis a mode with most of the controls disabled and with limitedfunctionality until the device is unlocked. This has the benefit in someembodiments of preventing the user from accidentally ending navigationmode prematurely. In some embodiments, unlocking the device requires aparticular gestural command on a specific part of the screen.

Some devices have a button that switches the screen off and/or puts thedevice into locked mode. Some devices have a timeout function thatswitches the screen off and/or puts the device into locked mode after acertain time has elapsed between user commands. Regardless of the waythat the applications get into locked mode, most such devices come outof locked mode with the same application running in the foreground asthe application running in the foreground when locked mode was entered.However, in the devices of some embodiments, regardless of whatapplication (or application launcher) is running in the foreground whenthe device is locked, if the navigation application is running in thebackground, then the application returns from locked mode directly intothe navigation application.

FIG. 35 illustrates a device 3500 of some embodiments that enters lockedmode with the navigation application running in the background and exitslocked mode with the navigation application running in the foreground.The figure shows the device 3500 in four stages 3501-3504. In stage3501, the application launcher 3520 in the foreground and the navigationapplication is running in the background. The navigation applicationrunning in the background is indicated by the navigation bar 3510 at thetop of the screen, just below the status bar 3515 and above theforeground application launcher 3520. As shown, in stage 3501 the userpushes a control 3590 to lock the screen.

In stage 3502, the device is in a locked mode (as indicated by theunlocking slider 3530 on the screen). In this stage, the map 3540 isshown on the locked screen and turn-by-turn directions are shown on theinformation bar 3550.

In stage 3503, the user has started to slide the unlocking slider 3530to the right in order to unlock the device. In this stage, the map 3540is displayed on the screen and turn-by-turn navigation directions areshown on the information bar 3550. In some embodiments (not shown), whenthe slider moves all the way to the right, the user is asked to enter apass code to unlock the screen. After the user successfully enters thepasscode, the screen is unlocked. In some embodiments, the directionsand/or the map are not shown under some circumstances in locked mode.For example, an interface for answering an incoming call may bedisplayed when a call comes in to the device and an interface fordealing with a call may be displayed when a call is in progress. Such aninterface may override the display of the directions in the informationbar, the display of the map, or both. Similarly, in some embodiments,other display views may replace the information bar, the map, or botheven though the navigation application is still running on the device.

However, after the screen is unlocked, the navigation map 3540 stays inthe foreground (instead of displaying application 3520 that was runningin the foreground prior to the locking of the screen). As shown in stage3504, the navigation application appears in full screen in theforeground. In this stage the screen is unlocked and navigationinstructions 3560 and the map 3540 are displayed on the screen. In someembodiments, the navigation application includes the map 3540 in thesame position as the map 3540 in the locked-screen view. Accordingly, insome embodiments, even for devices that ordinarily use a transition(e.g., a wipe or expansion of the new screen view from the center of thescreen) between locked-screen views and other views when returning fromlocked mode, the device in the transition from stage 3503 to stage 3504leaves the map in place and switches the other elements in the screen.That is, the map is constantly displayed during the transition fromstage 3503 to stage 3504, while the navigation bar 3510 and theunlocking slider 3530 disappear and the navigation instructions 3560appear instead. As stage 3504 shows, the device has returned from lockedmode directly into the navigation application, even though thenavigation application was running in the background, not the foregroundin stage 3501 before the device was locked.

FIG. 36 illustrates a device 3600 in some embodiments that enters lockedmode with the navigation application running in the foreground and exitsthe locked mode with the navigation application still running in theforeground. The figure shows the device in four stages 3601-3604. Instage 3601, the navigation application is running in the foreground anda map 3640 and navigation instructions 3660 are displayed on the screen.As shown, the user pushes a control 3690 to lock the screen.

In stage 3602, the device is placed into locked mode (as indicated bythe unlocking slider 3630 on the screen). In this stage, the map 3640 isshown on the locked screen and turn-by-turn directions are shown on theinformation bar 3650.

In stage 3603, the user has started to slide the unlocking slider 3630to the right in order to unlock the device. In this stage, the map 3640is displayed on the screen and turn-by-turn navigation directions areshown on the information bar 3650. When the slider moves all the way tothe right, the user is prompted (not shown) to enter the passcode tounlock the screen. After the user successfully enters the passcode, thescreen is unlocked. As mentioned above with respect to FIG. 35, in someembodiments, the directions and/or the map are not shown under somecircumstances in locked mode. For example, an interface for answering anincoming call is displayed in some embodiments when a call comes in tothe device and an interface for dealing with a call is displayed when acall is in progress. Such an interface overrides the display of thedirections in the information bar, the display of the map, or both.Similarly, in some embodiments, other display views may replace theinformation bar, the map, or both even though the navigation applicationis still running on the device.

As shown in stage 3604, the navigation application appears in theforeground. In this stage the screen is unlocked and the map 3640 andthe navigation instructions 3660 are displayed on the screen. In someembodiments, the navigation application includes the same map 3640 inthe same position as in the lock-screen view. Accordingly, in someembodiments, even for devices that would have a transition screen (e.g.,a wipe or expansion from the center) when returning from locked mode,the device in the transition from stage 3603 to stage 3604 leaves themap in place and, in some embodiments, switches the other elements inthe screen. That is, the map is constantly displayed during thetransition from stage 3603 to stage 3604, while the information bar 3650and the unlocking slider 3630 disappear and the navigation instructions3660 appear on the display. As stage 3604 shows, the device has returnedfrom locked mode back into the navigation application.

In the preceding two figures, the user pushes a control to enter alocked mode. In some embodiments, the user pushes such a control to turnthe display off. Later, when the display is turned back on, either bypressing the same control again, or by pressing another control, thenthe device shows the locked mode when the display turns on again.Similarly, in some embodiments, the device has a timeout function thatturns the display off after some particular amount of time has passedwithout the device receiving a command. In some embodiments, the deviceis in locked mode when the display turns on after such a lockout.

In addition to (or in some embodiments instead of) giving navigationinstructions on a navigation bar when other applications are in theforeground, the navigation applications of some embodiments also providenavigation instructions while the device is in a locked mode. FIG. 37illustrates a navigation application giving directions on a lockeddevice in some embodiments of the invention. The figure is shown in fourstages 3701-3704. In stage 3701, the device screen is displaying statusbar 3780, navigation bar 3710, map 3712, location indicator 3714, andunlocking slider 3716. One of ordinary skill in the art will understandthat other configurations and controls are possible within the scope ofsome embodiments.

In stage 3701, the device is close to the next navigation point,therefore navigation bar 3710 displays instructions to turn right in 500feet. In some embodiments (including the illustrated embodiment) thenavigation bar 3710 is translucent, allowing feature of the map 3712 tobe seen through the navigation bar 3710. The location indicator 3714indicates the location of the device, relative to the features of map3712. The map itself includes the road the device is on (Curb Road), andthe road that the navigation application is directing the user towards(T Road). Also displayed is a dark line 3718 showing the directed travelof the device and a lighter line 3719 showing the previous locations ofthe device along the navigation application's selected route. Theunlocking slider 3716, unlocks the device when activated. The unlockingslider 3716 is, however, unused in this figure.

As the device reaches a point 250 feet from the navigation point, thenavigation bar changes instructions as displayed in navigation bar 3720in stage 3702. The location indicator 3714 is at the same location, butthe map 3712 has moved down relative to the location indicator 3714. Thenew location of the map relative to the location indicator 3714 isanother way that the navigation application shows that the device hasmoved closer to the navigation point.

Similarly, in stage 3703, the navigation bar 3730 indicates that thenavigation point is only 100 feet away and the location indicator 3714is closer to the turn on the map. Finally, in stage 3704, the device hasgone around the corner and navigation bar 3740 is displaying the nextnavigation instruction. Although the transition between navigationinstructions is not shown in this figure, in some embodiments thetransition is similar to the described transition in background mode(with one instruction seemingly flipping up as if on a one side of asign and being replaced by another that seems to be on another side ofthe sign). In other embodiments, other transition methods are used toremove the old navigation instruction 3730 and replace it with the newnavigation instruction 3740 (in stage 3704). For instance, someembodiments simulate a new instruction sliding up or sideways while theold instruction slides in the same direction. Other embodiments simulatesliding the new instruction over the old instruction. Still otherembodiments simply have the old instruction disappear and be replaced bythe new instruction.

The new instructions are not the only indication that the turn has beenmade. The map 3712 has rotated so that the direction that the device istraveling in (along T Road) is shown on the map 3712 as being up. Thelighter line 3719 on the map 3712 now includes the corner that thedevice has just turned.

Although the location indicator 3714 is shown in FIG. 37 as always beingthe same size, in some embodiments, in one or both of the locked modeand the regular navigation mode, the location indicator is a differentsize depending on the zoom level. For example, in some embodiments, themore the map is zoomed in the larger the location indicator becomes.Similarly, the location indicator 3714 is always shown as having anarrow. However, in some embodiments, the arrow is not shown under somecircumstances. For example, in some embodiments, when the device is in abuilding (or otherwise off all the roads) rather than on a road, thearrow is not shown. The location indicator 3714 is shown as opaque inFIG. 37, however, in some embodiments, the location indicator istranslucent, semi-transparent, or transparent so as to show roads“underneath” it.

While operating in locked mode, the navigation application of someembodiments provides directions until the device reaches itsdestination. FIG. 38 illustrates the locked mode view of someembodiments when the device reaches its destination. The figure is shownin four stages 3801-3804. In stage 3801, the map 3840 shows lighter line3819 behind the current location indicator 3814. In front of locationindicator 3814, darker line 3818 ends at a circle 3812 that indicatesthe destination. According to navigation bar 3810, the destination is 50feet ahead.

Once the device reaches its destination in stage 3802, the navigationbar 3820 shows that the destination is on the right, darker line 3818 isno longer shown on the map 3840. In some embodiments, the device thendisplays a message that the device has “arrived” as shown in stage 3803.The navigation application then, in stage 3804, releases the lockedscreen to whatever its default configuration is when the navigationapplication is not providing navigation instructions. In the illustratedembodiment, the default configuration includes a time and date indicator3830.

This figure illustrates the locked mode view in a 2D map. However, themapping application of some embodiments may operate in the locked modewhile showing the map in 3D.

2. Notification Management

In some embodiments, devices notify their users of incoming textmessages and other noteworthy events. Even when such devices are in alocked mode, some such devices can still display notifications. However,leaving a notification on the screen for an extended period of time maydistract from navigation instructions also being displayed on thescreen. Accordingly, some embodiments briefly display a notification onthe screen and then make the notification accessible, but not visible.In some embodiments, there is a visible but unobtrusive sign indicatingthat there is a notification item waiting to be read. FIG. 39illustrates a locked view notification system of some embodiments. Thesystem is shown in four stages 3901-3904.

In stage 3901, the navigation bar 3910 is below the status bar 3980 atthe top of the screen displaying a navigation instruction. Anotification message 3912 is displayed on the screen over the map 3940to indicate that a text message has been received. The actual textmessage is not displayed in the illustrated embodiment, but embodimentsthat display the actual text message are within the scope of theinvention. Some embodiments display a name (if known) of the textmessage sender or a phone number from which the text message originatedin notification message 3912.

The application of some embodiments displays the notification for apreset length of time before the notification disappears, leaving thefull map 3940 visible again. Some applications display the notificationfor less than 5 seconds, some for 5 seconds, and some for more than 5seconds. Once the notification disappears, a drawer control 3922 appearsin stage 3902 in the navigation bar 3910. The application of someembodiments, including the illustrated application, allows the drawercontrol 3922 to be expanded (e.g., by a touch gesture that drags down onthe drawer control) in order to open a list of received notificationitems. Applications of other embodiments allow the drawer control to betapped to open the list, or double tapped to open the list. Similarly,other applications allow the drawer control to be selected by othermeans, (e.g., a selection such as a click on an associated cursorcontrol device).

In the illustrated embodiment, the drawer 3934 is shown as open in stage3903. In this stage 3903 the drawer, in this case including only onetext message 3932 and one missed call 3933, is shown in a list whichcovers the map from the bottom of the navigation bar 3910 to the top ofthe unlocking slider 3915. However, in some embodiments the drawer istranslucent, semi-transparent, or transparent, allowing the map to beseen through the list. In some embodiments, the drawer only partiallycovers the map 3940 (e.g., covers half the map, or only that portion ofthe map needed to show all the text messages and other notificationitems in the drawer). In some embodiments, if a new message ornotification that would normally be sent to the drawer arrives while thedrawer is open, the message will be added to the drawer right away (withor without displaying a pop up notification in various embodiments).

When the list of messages is too long to fit on the screen the list canbe scrolled up and down if necessary in some embodiments. When the useris finished looking at the list of messages, the user can close thedrawer by activating a control (e.g., a hardware or on screen controlsuch as a control that turns off the display) in some embodiments. Insome embodiments, the drawer will remain open until the user turns thedisplay off, and then back on again. The control could also include anynumber of controls activated by a gestural command such as a tap on thelist or elsewhere on the screen, a double-tap, or a sliding gesture(e.g., a sliding gesture up with part or all of the drawer as thecontrol) in some embodiments. The control could also include a button orother component of a mouse or other cursor control device, etc., in someembodiments.

Also, in addition to or instead of having a control to close the drawer,some embodiments display the opened drawer for varying lengths of timebefore it disappears, leaving the full map 3940 visible again as shownin stage 3904. Stage 3904 includes drawer control 3922. However, in someembodiments, after the drawer 3934 is closed, the drawer control 3922 isnot shown until a new message arrives.

After the drawer is closed, if and when another text message ornotification arrives, the stages 3901-3904 repeat with that new message,assuming that the navigation is still active. In some embodiments stage3904 happens only if the user closes the drawer. If the drawer remainsopen, then the display remains in stage 3903 in some embodiments.Furthermore, the drawer open stage 3903 may not immediately followstages 3901 and 3902. In some embodiments, if the user does not open thedrawer, stages 3901-3902 are repeated with each of multiple messagescoming in and the drawer remaining closed with the drawer control 3922displayed as the new message notifications appear.

In some cases, a user may decide to unlock the device before opening thedrawer 3934. In some embodiments, the normal behavior of the device whencoming out of locked mode with notifications is to list thenotifications on the screen. However, in some embodiments, when thenavigation application is running, opening into the navigationapplication takes priority over displaying the notification messages.Therefore the device of those embodiments unlocks and opens into thenavigation application rather than opening into a list of notificationmessages. In some such embodiments, a user can choose to open the listof notification messages after the navigation application is opened.FIG. 40 illustrates the viewing of notification messages after unlockinga device in some embodiments of the invention. The figure is shown insix stages 4001-4006.

In stage 4001, the navigation bar 4010 is below the status bar 4080 atthe top of the screen displaying a navigation instruction. Anotification message 4012 is displayed on the screen over the map 4040to indicate that a text message has been received. The actual textmessage is not displayed in the illustrated embodiment, but embodimentsthat display the actual text message are within the scope of theinvention. Some embodiments display the name of the sender, the phonenumber of the sender, or both in notification message 4012. Theapplication of different embodiments displays the notification forvarying lengths of time before it disappears, leaving the full map 4040visible again. Some applications display the notification for less than5 seconds, some for 5 seconds, and some for more than 5 seconds.

Once the notification disappears, a drawer control 4022 appears in stage4002 in the navigation bar 4010. Stage 4001 is identical to stage 3901of FIG. 39. However, in stage 4002, rather than opening the drawer 4022,the user instead unlocks the device with the unlocking slider 4016. Theuser has unlocked the device with the navigation application running inthe background, therefore, the navigation application appears in theforeground in stage 4003. As shown, the navigation application takespriority over displaying the notification messages.

The navigation application in some embodiments does not show a drawercontrol. However, by dragging the top center of the screen down (asshown in stage 4004) the user can cause the drawer 4044 to come down (asshown in stage 4005). In some embodiments, the drawer control 4022appears under the dragging finger as the finger drags the drawer 4044down. In other embodiments, when the navigation application is in theforeground, multiple drags must be employed. For example, one draggesture at the top of the screen is used to expose the drawer control4022 and a separate drag gesture on the drawer control 4022 is used toopen the drawer in some embodiments. Stage 4005 shows the drawer 4044fully extended and covering the entire screen. Text message 4052 appearsat the top of the screen.

In some embodiments, the drawer stays open until the user either closesthe drawer (at which point the navigation application appears again) orlocks the device. In some embodiments, the drawer can be closed bypulling up the drawer control 4022. In other embodiments, the drawercannot be closed by pulling up the drawer control up 4022, but can beclosed by some other control (e.g., a button or a gestural command). Forexample the device can be locked, e.g., by activating a control 4090which also closes the drawer in some embodiments. Some embodiments alsoautomatically close the drawer after a pre-determined amount of time. Insome embodiments, after the drawer is opened, either in locked mode orunlocked mode, once the drawer is closed the drawer is emptied and is nolonger accessible from the locked mode view, as shown in stage 4006, inwhich the drawer control 4022 is no longer present. That is, the drawercontrol 4022 will only be displayed again when a new notification isreceived. However, in other embodiments, the drawer control 4022 is notremoved, is only removed when certain methods of closing it areemployed, or is removed if the drawer is opened in the unlocked mode,but not if the drawer is opened in the locked mode.

In some embodiments, the drawer displays messages of different types inseparate areas. For example, some embodiments display text messages in aseparate area from “missed call” messages. In some embodiments thedrawer displays different types of messages in separate areas when it isopened in the unlocked mode, but the drawer in the locked mode does notdisplay different types of messages in separate areas. In otherembodiments the drawer displays different types of messages in separateareas when it is opened in the unlocked mode and the drawer in thelocked mode also displays different types of messages in separate areas.In other embodiments the drawer in locked mode uses separate areas fordifferent message types and the drawer in unlocked mode does not. Inother embodiments neither drawer separates message types.

3. Dynamically Turn On

Power saving is a feature of some embodiments of the application. Insome embodiments, the navigation application operating in locked modeswitches the screen on only when the device is approaching a navigationpoint or receives a notification. FIG. 41 illustrates a process 4100 forswitching the device screen on when approaching a navigation point insome embodiments of the invention. FIG. 41 will be described withrespect to FIG. 42, which will be briefly described first. FIG. 42illustrates multiple stages that a device goes through when no commandsare given to it while a navigation application runs in the background insome embodiments of the invention. FIG. 42 is illustrated in six stagesfrom 4201-4206. The various stages will be described at the appropriateplaces during the description of FIG. 41.

Process 4100 of FIG. 41 begins before the screen shuts off by displaying(at 4105) an application with the navigation application running in thebackground. Stage 4201 of FIG. 42 illustrates the pre-locked state ofthe device. This stage 4201 includes a foreground application 4212 (theapplication launching view) with the navigation bar 4210 below thestatus bar 4280 at the top of the screen, indicating that the navigationapplication is running in the background.

In some embodiments a device turns the screen off and enters locked modewhen it has received no commands in a pre-specified amount of time(e.g., 5 minutes, 15 minutes, etc.). The process determines (at 4110)whether any controls have been activated in the amount of timepre-specified for locking the device and turning of the screen. If anycontrols have been activated (other than one that shuts down the displayand/or locks the device right away) then the device resets its countdownto going into display off and locked mode.

When the process determines that enough time has passed, the processturns off (at 4115) the screen. In some embodiments, instead of or inaddition to the timeout screen deactivation, there is a control that theuser can select (e.g., a button) that puts the device into locked mode.In some embodiments, the timeout screen deactivation occurs when someapplications are running, but not when other applications are running.For example, in some embodiments, when the navigation application isrunning in the foreground the device does not shut down the screen aftera preset time. Furthermore, in some embodiments, the device doesn'ttimeout when the navigation application is running in the backgroundeither.

Operation 4115 is illustrated in stage 4202 of FIG. 42. Stage 4202 showsthe screen in black because it has been turned off either by a timeout,a control, or in some other way. While the screen is off and the devicetravels toward the next navigation point the process 4100 repeatedlydetermines (at 4120) whether the device is near the next navigationpoint. If the device is not near the next navigation point, the devicewill keep checking whether it is near the navigation point. “Near” meansdifferent distances in the application of different embodiments.

In different embodiments, the device determines that it is near anavigation point when the device is 1000 feet from the navigation point,or 500 feet, or 250 feet, or any other particular distance. Once process4100 determines (at 4120) that the device is near the navigation point,the process turns on (at 4125) an ambient light sensor. In someembodiments the ambient light sensor is part of a camera of the device.In other embodiments, the ambient light sensor is not part of a cameraof the device. In some embodiments, the ambient light sensor is on atall times. In some embodiments, the ambient light sensor is a passiveelement that doesn't need to be powered on to function. The ambientlight sensor determines how much light is present around the device. Ifthere is a large amount of light, then the screen would have to beturned on at a high level of brightness to be seen against the existinglight. However, if there if a low amount of ambient light, then thescreen could be turned on at a dimmer level and still be bright enoughto be seen in the lower ambient light.

Once the light level is determined, the process 4100 turns on (at 4130)the screen at a brightness level in accord with the ambient light levelsdetected by the ambient light sensor. The screen then displays (at 4135)a countdown to the next navigation point. This is illustrated in stage4203 of FIG. 42. The figure shows navigation bar 4230 with an arrowindicating a right turn and instructions to turn right in 1000 feet. Theprocess then determines (at 4140) whether the navigation point has beenpassed. If the navigation point has not been passed, then the process4100 returns to operation 4135. The process then continues to displaythe countdown to the next navigation point. Part of the countdown isshown in stage 4204 in FIG. 42. In stage 4204, navigation bar 4240indicates that there are 200 feet left to the right turn. Once thedevice passes the navigation point (in this case making the right turn),process 4100 determines (at 4145) whether the device is at itsdestination. If the device is at its destination, then the navigationprocess ends. If the device is not at its destination then the processdisplays (at 4150) the next navigation instruction. This is illustratedin stage 4205 in FIG. 42. In this stage navigation bar 4250 displays 2.8miles, go straight.

If the process 4100 determines (at 4155) that the next navigation pointis near, then the process returns to operation 4135 and counts down tothe next navigation point. However, that is not the case in FIG. 42. Ifthe process determines (at 4155) that the device is not near the nextnavigation point, then the process 4100 turns the screen off (at 4115).This is shown in stage 4206 which shows the dark screen. One of ordinaryskill in the art will understand that the words “Power saving mode” inFIG. 42, stages 4202 and 4206 are meant to conceptually illustrate thatthe display is turned off and that they are not physically displayed onthe screen during power saving mode in some embodiments.

The above described figure shows the device switching the display on asit nears predetermined navigation points, and switching the display offwhen it is not nearing the preset navigation points. However, in someembodiments, the device also turns the display on if the user deviatesfrom the prescribed route (e.g., the user takes a wrong turn). In somesuch embodiments, the device displays a “rerouting” message until thedevice has calculated a new route. In some embodiments, the device thendisplays the next navigation instruction and then turns off the displayunless the next navigation point is within the threshold distance.

In a similar manner to the way the navigation application of someembodiments turns on the screen in locked mode when the deviceapproaches a navigation point, the device of some embodiments turns onthe screen when a notification is received while the navigation programis running. FIG. 43 conceptually illustrates a process 4300 of someembodiments for turning on the screen when a notification message isreceived. Process 4300 will be described with reference to previouslydescribed FIG. 39. Process 4300 begins by turning the screen off (at4305). The screen can be turned off for any of the reasons discussedwith respect to FIG. 41. The process then waits (at 4310) until itreceives a notification. When the process 4300 receives a notification,it turns on (at 4315) the ambient light sensor (as described above inoperation 4125 of FIG. 41). The process then turns on (at 4320) thescreen at a brightness set according to the ambient light level asdetected by the ambient light sensor. The process then displays (at4325) the notification. This is shown in FIG. 39 in stage 3901 as popupmessage 3912. The process then puts (at 4330) the notification in adrawer as described with respect to stage 3902 of FIG. 39.

The process then determines (at 4335) whether the drawer has been opened(e.g., by the user sliding a drawer control 3922) before a time limit.If the drawer has not been opened within the time limit then the processturns the screen off (at 4305) again. If the drawer has been openedbefore the time limit, then the messages are displayed (at 4340), e.g.,as shown in FIG. 39 (as stage 3903, with message 3932 displayed). Theprocess then determines (at 4345) whether the drawer has been closed. Ifthe drawer has been closed then the process returns to operation 4305and turns off the screen after a timeout period. That is, in theapplications of some embodiments, the application waits for some amountof time after the drawer is closed before turning off the screen.

In some embodiments, if the process 4300 determines (at 4345) that thedrawer remains open, then the process determines (at 4350) whether atimeout period has been reached. If the timeout period has not beenreached, then the process continues to display (at 4340) the messages.If the time limit runs out before the drawer is closed by the user, thenthe process turns the screen off (at 4305). In some embodiments, if theuser is sending commands to the device (e.g., scrolling through themessages) then the countdown to the time limit will not begin until thedevice stops receiving commands from the user.

One of ordinary skill in the art will understand that although theflowcharts for process 4300 of FIG. 43 and the process 4100 of FIG. 41are being described separately, in some embodiments, they proceedsimultaneously and the screen will be on when either one of theprocesses requires it. In some cases it will already be on fornotification reasons when a navigation point becomes near. In thesecases, rather than switching on (at 4130) as process 4100 dictates, thescreen would simply remain on, even if process 4300 required that itturn off (at 4305) Similarly, processes 4100 and 4300 will continue insome embodiments until either the device is unlocked, or the destinationis reached (as shown in operation 4145 of process 4100 in FIG. 41).

As described above, the device in locked mode has a limited number ofactive controls. However, in some embodiments, while the locked mode isoperative, the map on the lock screen can be moved to one side or up anddown, to a greater or lesser degree, by a gestural command in thedirection that the user wishes to move the map. In some embodiments,when the device is released, the map returns to its default position.

IV. Electronic System

Many of the above-described features and applications are implemented assoftware processes that are specified as a set of instructions recordedon a computer readable storage medium (also referred to as computerreadable medium). When these instructions are executed by one or morecomputational or processing unit(s) (e.g., one or more processors, coresof processors, or other processing units), they cause the processingunit(s) to perform the actions indicated in the instructions. Examplesof computer readable media include, but are not limited to, CD-ROMs,flash drives, random access memory (RAM) chips, hard drives, erasableprogrammable read-only memories (EPROMs), electrically erasableprogrammable read-only memories (EEPROMs), etc. The computer readablemedia does not include carrier waves and electronic signals passingwirelessly or over wired connections.

In this specification, the term “software” is meant to include firmwareresiding in read-only memory or applications stored in magnetic storagewhich can be read into memory for processing by a processor. Also, insome embodiments, multiple software inventions can be implemented assub-parts of a larger program while remaining distinct softwareinventions. In some embodiments, multiple software inventions can alsobe implemented as separate programs. Finally, any combination ofseparate programs that together implement a software invention describedhere is within the scope of the invention. In some embodiments, thesoftware programs, when installed to operate on one or more electronicsystems, define one or more specific machine implementations thatexecute and perform the operations of the software programs.

A. Mobile Device

The mapping and navigation applications of some embodiments operate onmobile devices, such as smart phones (e.g., iPhones®) and tablets (e.g.,iPads®). FIG. 44 is an example of an architecture 4400 of such a mobilecomputing device. Examples of mobile computing devices includesmartphones, tablets, laptops, etc. As shown, the mobile computingdevice 4400 includes one or more processing units 4405, a memoryinterface 4410 and a peripherals interface 4415.

The peripherals interface 4415 is coupled to various sensors andsubsystems, including a camera subsystem 4420, a wireless communicationsubsystem(s) 4425, an audio subsystem 4430, an I/O subsystem 4435, etc.The peripherals interface 4415 enables communication between theprocessing units 4405 and various peripherals. For example, anorientation sensor 4445 (e.g., a gyroscope) and an acceleration sensor4450 (e.g., an accelerometer) is coupled to the peripherals interface4415 to facilitate orientation and acceleration functions.

The camera subsystem 4420 is coupled to one or more optical sensors 4440(e.g., a charged coupled device (CCD) optical sensor, a complementarymetal-oxide-semiconductor (CMOS) optical sensor, etc.). The camerasubsystem 4420 coupled with the optical sensors 4440 facilitates camerafunctions, such as image and/or video data capturing. The wirelesscommunication subsystem 4425 serves to facilitate communicationfunctions. In some embodiments, the wireless communication subsystem4425 includes radio frequency receivers and transmitters, and opticalreceivers and transmitters (not shown in FIG. 44). These receivers andtransmitters of some embodiments are implemented to operate over one ormore communication networks such as a GSM network, a Wi-Fi network, aBluetooth network, etc. The audio subsystem 4430 is coupled to a speakerto output audio (e.g., to output voice navigation instructions).Additionally, the audio subsystem 4430 is coupled to a microphone tofacilitate voice-enabled functions, such as voice recognition (e.g., forsearching), digital recording, etc.

The I/O subsystem 4435 involves the transfer between input/outputperipheral devices, such as a display, a touch screen, etc., and thedata bus of the processing units 4405 through the peripherals interface4415. The I/O subsystem 4435 includes a touch-screen controller 4455 andother input controllers 4460 to facilitate the transfer betweeninput/output peripheral devices and the data bus of the processing units4405. As shown, the touch-screen controller 4455 is coupled to a touchscreen 4465. The touch-screen controller 4455 detects contact andmovement on the touch screen 4465 using any of multiple touchsensitivity technologies. The other input controllers 4460 are coupledto other input/control devices, such as one or more buttons. Someembodiments include a near-touch sensitive screen and a correspondingcontroller that can detect near-touch interactions instead of or inaddition to touch interactions.

The memory interface 4410 is coupled to memory 4470. In someembodiments, the memory 4470 includes volatile memory (e.g., high-speedrandom access memory), non-volatile memory (e.g., flash memory), acombination of volatile and non-volatile memory, and/or any other typeof memory. As illustrated in FIG. 44, the memory 4470 stores anoperating system (OS) 4472. The OS 4472 includes instructions forhandling basic system services and for performing hardware dependenttasks.

The memory 4470 also includes communication instructions 4474 tofacilitate communicating with one or more additional devices; graphicaluser interface instructions 4476 to facilitate graphic user interfaceprocessing; image processing instructions 4478 to facilitateimage-related processing and functions; input processing instructions4480 to facilitate input-related (e.g., touch input) processes andfunctions; audio processing instructions 4482 to facilitateaudio-related processes and functions; and camera instructions 4484 tofacilitate camera-related processes and functions. The instructionsdescribed above are merely exemplary and the memory 4470 includesadditional and/or other instructions in some embodiments. For instance,the memory for a smartphone may include phone instructions to facilitatephone-related processes and functions. Additionally, the memory mayinclude instructions for a mapping and navigation application as well asother applications. The above-identified instructions need not beimplemented as separate software programs or modules. Various functionsof the mobile computing device can be implemented in hardware and/or insoftware, including in one or more signal processing and/or applicationspecific integrated circuits.

While the components illustrated in FIG. 44 are shown as separatecomponents, one of ordinary skill in the art will recognize that two ormore components may be integrated into one or more integrated circuits.In addition, two or more components may be coupled together by one ormore communication buses or signal lines. Also, while many of thefunctions have been described as being performed by one component, oneof ordinary skill in the art will realize that the functions describedwith respect to FIG. 44 may be split into two or more integratedcircuits.

B. Computer System

FIG. 45 conceptually illustrates another example of an electronic system4500 with which some embodiments of the invention are implemented. Theelectronic system 4500 may be a computer (e.g., a desktop computer,personal computer, tablet computer, etc.), phone, PDA, or any other sortof electronic or computing device. Such an electronic system includesvarious types of computer readable media and interfaces for variousother types of computer readable media. Electronic system 4500 includesa bus 4505, processing unit(s) 4510, a graphics processing unit (GPU)4515, a system memory 4520, a network 4525, a read-only memory 4530, apermanent storage device 4535, input devices 4540, and output devices4545.

The bus 4505 collectively represents all system, peripheral, and chipsetbuses that communicatively connect the numerous internal devices of theelectronic system 4500. For instance, the bus 4505 communicativelyconnects the processing unit(s) 4510 with the read-only memory 4530, theGPU 4515, the system memory 4520, and the permanent storage device 4535.

From these various memory units, the processing unit(s) 4510 retrievesinstructions to execute and data to process in order to execute theprocesses of the invention. The processing unit(s) may be a singleprocessor or a multi-core processor in different embodiments. Someinstructions are passed to and executed by the GPU 4515. The GPU 4515can offload various computations or complement the image processingprovided by the processing unit(s) 4510. In some embodiments, suchfunctionality can be provided using CoreImage's kernel shading language.

The read-only-memory (ROM) 4530 stores static data and instructions thatare needed by the processing unit(s) 4510 and other modules of theelectronic system. The permanent storage device 4535, on the other hand,is a read-and-write memory device. This device is a non-volatile memoryunit that stores instructions and data even when the electronic system4500 is off. Some embodiments of the invention use a mass-storage device(such as a magnetic or optical disk and its corresponding disk drive,integrated flash memory) as the permanent storage device 4535.

Other embodiments use a removable storage device (such as a floppy disk,flash memory device, etc., and its corresponding drive) as the permanentstorage device. Like the permanent storage device 4535, the systemmemory 4520 is a read-and-write memory device. However, unlike storagedevice 4535, the system memory 4520 is a volatile read-and-write memory,such a random access memory. The system memory 4520 stores some of theinstructions and data that the processor needs at runtime. In someembodiments, the invention's processes are stored in the system memory4520, the permanent storage device 4535, and/or the read-only memory4530. For example, the various memory units include instructions forprocessing multimedia clips in accordance with some embodiments. Fromthese various memory units, the processing unit(s) 4510 retrievesinstructions to execute and data to process in order to execute theprocesses of some embodiments.

The bus 4505 also connects to the input and output devices 4540 and4545. The input devices 4540 enable the user to communicate informationand select commands to the electronic system. The input devices 4540include alphanumeric keyboards and pointing devices (also called “cursorcontrol devices”), cameras (e.g., webcams), microphones or similardevices for receiving voice commands, etc. The output devices 4545display images generated by the electronic system or otherwise outputdata. The output devices 4545 include printers and display devices, suchas cathode ray tubes (CRT) or liquid crystal displays (LCD), as well asspeakers or similar audio output devices. Some embodiments includedevices such as a touchscreen that function as both input and outputdevices.

Finally, as shown in FIG. 45, bus 4505 also couples electronic system4500 to a network 4525 through a network adapter (not shown). In thismanner, the computer can be a part of a network of computers (such as alocal area network (“LAN”), a wide area network (“WAN”), or anIntranet), or a network of networks, such as the Internet. Any or allcomponents of electronic system 4500 may be used in conjunction with theinvention.

Some embodiments include electronic components, such as microprocessors,storage and memory that store computer program instructions in amachine-readable or computer-readable medium (alternatively referred toas computer-readable storage media, machine-readable media, ormachine-readable storage media). Some examples of such computer-readablemedia include RAM, ROM, read-only compact discs (CD-ROM), recordablecompact discs (CD-R), rewritable compact discs (CD-RW), read-onlydigital versatile discs (e.g., DVD-ROM, dual-layer DVD-ROM), a varietyof recordable/rewritable DVDs (e.g., DVD-RAM, DVD-RW, DVD+RW, etc.),flash memory (e.g., SD cards, mini-SD cards, micro-SD cards, etc.),magnetic and/or solid state hard drives, read-only and recordableBlu-Ray® discs, ultra density optical discs, any other optical ormagnetic media, and floppy disks. The computer-readable media may storea computer program that is executable by at least one processing unitand includes sets of instructions for performing various operations.Examples of computer programs or computer code include machine code,such as is produced by a compiler, and files including higher-level codethat are executed by a computer, an electronic component, or amicroprocessor using an interpreter.

While the above discussion primarily refers to microprocessor ormulti-core processors that execute software, some embodiments areperformed by one or more integrated circuits, such as applicationspecific integrated circuits (ASICs) or field programmable gate arrays(FPGAs). In some embodiments, such integrated circuits executeinstructions that are stored on the circuit itself. In addition, someembodiments execute software stored in programmable logic devices(PLDs), ROM, or RAM devices.

As used in this specification and any claims of this application, theterms “computer”, “server”, “processor”, and “memory” all refer toelectronic or other technological devices. These terms exclude people orgroups of people. For the purposes of the specification, the termsdisplay or displaying means displaying on an electronic device. As usedin this specification and any claims of this application, the terms“computer readable medium,” “computer readable media,” and “machinereadable medium” are entirely restricted to tangible, physical objectsthat store information in a form that is readable by a computer. Theseterms exclude any wireless signals, wired download signals, and anyother ephemeral signals.

V. Map Service Environment

Various embodiments may operate within a map service operatingenvironment. FIG. 46 illustrates a map service operating environment,according to some embodiments. A map service 4630 (also referred to asmapping service) may provide map services for one or more client devices4602 a-4602 c in communication with the map service 4630 through variouscommunication methods and protocols. A map service 4630 in someembodiments provides map information and other map-related data, such astwo-dimensional map image data (e.g., aerial view of roads utilizingsatellite imagery), three-dimensional map image data (e.g., traversablemap with three-dimensional features, such as buildings), route anddirection calculations (e.g., ferry route calculations or directionsbetween two points for a pedestrian), real-time navigation data (e.g.,turn-by-turn visual navigation data in two or three dimensions),location data (e.g., where the client device is currently located), andother geographic data (e.g., wireless network coverage, weather, trafficinformation, or nearby points-of-interest). In various embodiments, themap service data may include localized labels for different countries orregions. Localized labels may be utilized to present map labels (e.g.,street names, city names, points of interest) in different languages onclient devices. Client devices 4602 a-4602 c may utilize these mapservices by obtaining map service data. Client devices 4602 a-4602 c mayimplement various techniques to process map service data. Client devices4602 a-4602 c may then provide map services to various entities,including, but not limited to, users, internal software or hardwaremodules, and/or other systems or devices external to the client devices4602 a-4602 c.

In some embodiments, a map service is implemented by one or more nodesin a distributed computing system. Each node may be assigned one or moreservices or components of a map service. Some nodes may be assigned thesame map service or component of a map service. A load balancing node insome embodiments distributes access or requests to other nodes within amap service. In some embodiments a map service is implemented as asingle system, such as a single server. Different modules or hardwaredevices within a server may implement one or more of the variousservices provided by a map service.

A map service in some embodiments provides map services by generatingmap service data in various formats. In some embodiments, one format ofmap service data is map image data. Map image data provides image datato a client device so that the client device may process the image data(e.g., rendering and/or displaying the image data as a two-dimensionalor three-dimensional map). Map image data, whether in two or threedimensions, may specify one or more map tiles. A map tile may be aportion of a larger map image. Assembling together the map tiles of amap produces the original map. Tiles may be generated from map imagedata, routing or navigation data, or any other map service data. In someembodiments map tiles are raster-based map tiles, with tile sizesranging from any size both larger and smaller than a commonly-used 256pixel by 256 pixel tile. Raster-based map tiles may be encoded in anynumber of standard digital image representations including, but notlimited to, Bitmap (.bmp), Graphics Interchange Format (.gif), JointPhotographic Experts Group (.jpg, .jpeg, etc.), Portable NetworksGraphic (.png), or Tagged Image File Format (.tiff). In someembodiments, map tiles are vector-based map tiles, encoded using vectorgraphics, including, but not limited to, Scalable Vector Graphics (.svg)or a Drawing File (.drw). Some embodiments also include tiles with acombination of vector and raster data. Metadata or other informationpertaining to the map tile may also be included within or along with amap tile, providing further map service data to a client device. Invarious embodiments, a map tile is encoded for transport utilizingvarious standards and/or protocols, some of which are described inexamples below.

In various embodiments, map tiles may be constructed from image data ofdifferent resolutions depending on zoom level. For instance, for lowzoom level (e.g., world or globe view), the resolution of map or imagedata need not be as high relative to the resolution at a high zoom level(e.g., city or street level). For example, when in a globe view, theremay be no need to render street level artifacts as such objects would beso small as to be negligible in many cases.

A map service in some embodiments performs various techniques to analyzea map tile before encoding the tile for transport. This analysis mayoptimize map service performance for both client devices and a mapservice. In some embodiments map tiles are analyzed for complexity,according to vector-based graphic techniques, and constructed utilizingcomplex and non-complex layers. Map tiles may also be analyzed forcommon image data or patterns that may be rendered as image textures andconstructed by relying on image masks. In some embodiments, raster-basedimage data in a map tile contains certain mask values, which areassociated with one or more textures. Some embodiments also analyze maptiles for specified features that may be associated with certain mapstyles that contain style identifiers.

Other map services generate map service data relying upon various dataformats separate from a map tile in some embodiments. For instance, mapservices that provide location data may utilize data formats conformingto location service protocols, such as, but not limited to, RadioResource Location services Protocol (RRLP), TIA 801 for Code DivisionMultiple Access (CDMA), Radio Resource Control (RRC) position protocol,or LTE Positioning Protocol (LPP). Embodiments may also receive orrequest data from client devices identifying device capabilities orattributes (e.g., hardware specifications or operating system version)or communication capabilities (e.g., device communication bandwidth asdetermined by wireless signal strength or wire or wireless networktype).

A map service may obtain map service data from internal or externalsources. For example, satellite imagery used in map image data may beobtained from external services, or internal systems, storage devices,or nodes. Other examples may include, but are not limited to, GPSassistance servers, wireless network coverage databases, business orpersonal directories, weather data, government information (e.g.,construction updates or road name changes), or traffic reports. Someembodiments of a map service may update map service data (e.g., wirelessnetwork coverage) for analyzing future requests from client devices.

Various embodiments of a map service may respond to client devicerequests for map services. These requests may be for a specific maps orportions of a map. Some embodiments format requests for a map asrequests for certain map tiles. In some embodiments, requests alsosupply the map service with starting locations (or current locations)and destination locations for a route calculation. A client device mayalso request map service rendering information, such as map textures orstyle sheets. In at least some embodiments, requests are also one of aseries of requests implementing turn-by-turn navigation. Requests forother geographic data may include, but are not limited to, requests forcurrent location, wireless network coverage, weather, trafficinformation, or nearby points-of-interest.

A map service, in some embodiments, analyzes client device requests tooptimize a device or map service operation. For instance, a map servicemay recognize that the location of a client device is in an area of poorcommunications (e.g., weak wireless signal) and send more map servicedata to supply a client device in the event of loss in communication orsend instructions to utilize different client hardware (e.g.,orientation sensors) or software (e.g., utilize wireless locationservices or Wi-Fi positioning instead of GPS-based services). In anotherexample, a map service may analyze a client device request forvector-based map image data and determine that raster-based map databetter optimizes the map image data according to the image's complexity.Embodiments of other map services may perform similar analysis on clientdevice requests and, as such, the above examples are not intended to belimiting.

Various embodiments of client devices (e.g., client devices 4602 a-4602c) are implemented on different portable-multifunction device types.Client devices 4602 a-4602 c utilize map service 4630 through variouscommunication methods and protocols. In some embodiments, client devices4602 a-4602 c obtain map service data from map service 4630. Clientdevices 4602 a-4602 c request or receive map service data. Clientdevices 4602 a-4602 c then process map service data (e.g., render and/ordisplay the data) and may send the data to another software or hardwaremodule on the device or to an external device or system.

A client device, according to some embodiments, implements techniques torender and/or display maps. These maps may be requested or received invarious formats, such as map tiles described above. A client device mayrender a map in two-dimensional or three-dimensional views. Someembodiments of a client device display a rendered map and allow a user,system, or device providing input to manipulate a virtual camera in themap, changing the map display according to the virtual camera'sposition, orientation, and field-of-view. Various forms and inputdevices are implemented to manipulate a virtual camera. In someembodiments, touch input, through certain single or combination gestures(e.g., touch-and-hold or a swipe) manipulate the virtual camera. Otherembodiments allow manipulation of the device's physical location tomanipulate a virtual camera. For instance, a client device may be tiltedup from its current position to manipulate the virtual camera to rotateup. In another example, a client device may be tilted forward from itscurrent position to move the virtual camera forward. Other input devicesto the client device may be implemented including, but not limited to,auditory input (e.g., spoken words), a physical keyboard, mouse, and/ora joystick.

Some embodiments provide various visual feedback to virtual cameramanipulations, such as displaying an animation of possible virtualcamera manipulations when transitioning from two-dimensional map viewsto three-dimensional map views. Some embodiments also allow input toselect a map feature or object (e.g., a building) and highlight theobject, producing a blur effect that maintains the virtual camera'sperception of three-dimensional space.

In some embodiments, a client device implements a navigation system(e.g., turn-by-turn navigation). A navigation system provides directionsor route information, which may be displayed to a user. Some embodimentsof a client device request directions or a route calculation from a mapservice. A client device may receive map image data and route data froma map service. In some embodiments, a client device implements aturn-by-turn navigation system, which provides real-time route anddirection information based upon location information and routeinformation received from a map service and/or other location system,such as a Global Positioning Satellite (GPS). A client device maydisplay map image data that reflects the current location of the clientdevice and update the map image data in real-time. A navigation systemmay provide auditory or visual directions to follow a certain route.

A virtual camera is implemented to manipulate navigation map dataaccording to some embodiments. In some embodiments, the client devicesallow the device to adjust the virtual camera display orientation tobias toward the route destination. Some embodiments also allow thevirtual camera to navigate turns by simulating the inertial motion ofthe virtual camera.

Client devices implement various techniques to utilize map service datafrom map service. Some embodiments implement some techniques to optimizerendering of two-dimensional and three-dimensional map image data. Insome embodiments, a client device locally stores rendering information.For instance, a client stores a style sheet, which provides renderingdirections for image data containing style identifiers. In anotherexample, common image textures may be stored to decrease the amount ofmap image data transferred from a map service. Client devices indifferent embodiments implement various modeling techniques to rendertwo-dimensional and three-dimensional map image data, examples of whichinclude, but are not limited to: generating three-dimensional buildingsout of two-dimensional building footprint data; modeling two-dimensionaland three-dimensional map objects to determine the client devicecommunication environment; generating models to determine whether maplabels are seen from a certain virtual camera position; and generatingmodels to smooth transitions between map image data. In someembodiments, the client devices also order or prioritize map servicedata in certain techniques. For instance, a client device detects themotion or velocity of a virtual camera, which if exceeding certainthreshold values, lower-detail image data is loaded and rendered forcertain areas. Other examples include: rendering vector-based curves asa series of points, preloading map image data for areas of poorcommunication with a map service, adapting textures based on displayzoom level, or rendering map image data according to complexity.

In some embodiments, client devices communicate utilizing various dataformats separate from a map tile. For instance, some client devicesimplement Assisted Global Positioning Satellites (A-GPS) and communicatewith location services that utilize data formats conforming to locationservice protocols, such as, but not limited to, Radio Resource Locationservices Protocol (RRLP), TIA 801 for Code Division Multiple Access(CDMA), Radio Resource Control (RRC) position protocol, or LTEPositioning Protocol (LPP). Client devices may also receive GPS signalsdirectly. Embodiments may also send data, with or without solicitationfrom a map service, identifying the client device's capabilities orattributes (e.g., hardware specifications or operating system version)or communication capabilities (e.g., device communication bandwidth asdetermined by wireless signal strength or wire or wireless networktype).

FIG. 46 illustrates one possible embodiment of an operating environment4600 for a map service 4630 and client devices 4602 a-4602 c. In someembodiments, devices 4602 a, 4602 b, and 4602 c communicate over one ormore wire or wireless networks 4610. For example, wireless network 4610,such as a cellular network, can communicate with a wide area network(WAN) 4620, such as the Internet, by use of gateway 4614. A gateway 4614in some embodiments provides a packet oriented mobile data service, suchas General Packet Radio Service (GPRS), or other mobile data serviceallowing wireless networks to transmit data to other networks, such aswide area network 4620. Likewise, access device 4612 (e.g., IEEE 802.11gwireless access device) provides communication access to WAN 4620.Devices 4602 a and 4602 b can be any portable electronic or computingdevice capable of communicating with a map service. Device 4602 c can beany non-portable electronic or computing device capable of communicatingwith a map service.

In some embodiments, both voice and data communications are establishedover wireless network 4610 and access device 4612. For instance, device4602 a can place and receive phone calls (e.g., using voice overInternet Protocol (VoIP) protocols), send and receive e-mail messages(e.g., using Simple Mail Transfer Protocol (SMTP) or Post OfficeProtocol 3 (POP3)), and retrieve electronic documents and/or streams,such as web pages, photographs, and videos, over wireless network 4610,gateway 4614, and WAN 4620 (e.g., using Transmission ControlProtocol/Internet Protocol (TCP/IP) or User Datagram Protocol (UDP)).Likewise, in some implementations, devices 4602 b and 4602 c can placeand receive phone calls, send and receive e-mail messages, and retrieveelectronic documents over access device 4612 and WAN 4620. In variousembodiments, any of the illustrated client devices may communicate withmap service 4630 and/or other service(s) 4650 using a persistentconnection established in accordance with one or more securityprotocols, such as the Secure Sockets Layer (SSL) protocol or theTransport Layer Security (TLS) protocol.

Devices 4602 a and 4602 b can also establish communications by othermeans. For example, wireless device 4602 a can communicate with otherwireless devices (e.g., other devices 4602 b, cell phones, etc.) overthe wireless network 4610. Likewise devices 4602 a and 4602 b canestablish peer-to-peer communications 4640 (e.g., a personal areanetwork) by use of one or more communication subsystems, such asBluetooth® communication from Bluetooth Special Interest Group, Inc. ofKirkland, Wash. Device 4602 c can also establish peer to peercommunications with devices 4602 a or 4602 b (not shown). Othercommunication protocols and topologies can also be implemented. Devices4602 a and 4602 b may also receive Global Positioning Satellite (GPS)signals from GPS satellites 4660.

Devices 4602 a, 4602 b, and 4602 c can communicate with map service 4630over one or more wired and/or wireless networks, 4612 or 4610. Forinstance, map service 4630 can provide map service data to renderingdevices 4602 a, 4602 b, and 4602 c. Map service 4630 may alsocommunicate with other services 4650 to obtain data to implement mapservices. Map service 4630 and other services 4650 may also receive GPSsignals from GPS satellites 4660.

In various embodiments, map service 4630 and/or other service(s) 4650are configured to process search requests from any of the clientdevices. Search requests may include but are not limited to queries forbusinesses, addresses, residential locations, points of interest, orsome combination thereof. Map service 4630 and/or other service(s) 4650may be configured to return results related to a variety of parametersincluding but not limited to a location entered into an address bar orother text entry field (including abbreviations and/or other shorthandnotation), a current map view (e.g., user may be viewing one location onthe multifunction device while residing in another location), currentlocation of the user (e.g., in cases where the current map view did notinclude search results), and the current route (if any). In variousembodiments, these parameters may affect the composition of the searchresults (and/or the ordering of the search results) based on differentpriority weightings. In various embodiments, the search results that arereturned may be a subset of results selected based on specific criteriaincluding but not limited to a quantity of times the search result(e.g., a particular point of interest) has been requested, a measure ofquality associated with the search result (e.g., highest user oreditorial review rating), and/or the volume of reviews for the searchresults (e.g., the number of times the search result has been review orrated).

In various embodiments, map service 4630 and/or other service(s) 4650are configured to provide auto-complete search results that aredisplayed on the client device, such as within the mapping application.For instance, auto-complete search results may populate a portion of thescreen as the user enters one or more search keywords on themultifunction device. In some cases, this feature may save the user timeas the desired search result may be displayed before the user enters thefull search query. In various embodiments, the auto complete searchresults may be search results found by the client on the client device(e.g., bookmarks or contacts), search results found elsewhere (e.g.,from the Internet) by map service 4630 and/or other service(s) 4650,and/or some combination thereof. As is the case with commands, any ofthe search queries may be entered by the user via voice or throughtyping. The multifunction device may be configured to display searchresults graphically within any of the map display described herein. Forinstance, a pin or other graphical indicator may specify locations ofsearch results as points of interest. In various embodiments, responsiveto a user selection of one of these points of interest (e.g., a touchselection, such as a tap), the multifunction device is configured todisplay additional information about the selected point of interestincluding but not limited to ratings, reviews or review snippets, hoursof operation, store status (e.g., open for business, permanently closed,etc.), and/or images of a storefront for the point of interest. Invarious embodiments, any of this information may be displayed on agraphical information card that is displayed in response to the user'sselection of the point of interest.

In various embodiments, map service 4630 and/or other service(s) 4650provide one or more feedback mechanisms to receive feedback from clientdevices 4602 a-4602 c. For instance, client devices may provide feedbackon search results to map service 4630 and/or other service(s) 4650(e.g., feedback specifying ratings, reviews, temporary or permanentbusiness closures, errors etc.); this feedback may be used to updateinformation about points of interest in order to provide more accurateor more up-to-date search results in the future. In some embodiments,map service 4630 and/or other service(s) 4650 may provide testinginformation to the client device (e.g., an A/B test) to determine whichsearch results are best. For instance, at random intervals, the clientdevice may receive and present two search results to a user and allowthe user to indicate the best result. The client device may report thetest results to map service 4630 and/or other service(s) 4650 to improvefuture search results based on the chosen testing technique, such as anA/B test technique in which a baseline control sample is compared to avariety of single-variable test samples in order to improve results.

While the invention has been described with reference to numerousspecific details, one of ordinary skill in the art will recognize thatthe invention can be embodied in other specific forms without departingfrom the spirit of the invention. For instance, many of the figuresillustrate various touch gestures (e.g., taps, double taps, swipegestures, press and hold gestures, etc.). However, many of theillustrated operations could be performed via different touch gestures(e.g., a swipe instead of a tap, etc.) or by non-touch input (e.g.,using a cursor controller, a keyboard, a touchpad/trackpad, a near-touchsensitive screen, etc.). In addition, a number of the figuresconceptually illustrate processes. The specific operations of theseprocesses may not be performed in the exact order shown and described.The specific operations may not be performed in one continuous series ofoperations, and different specific operations may be performed indifferent embodiments. Furthermore, the process could be implementedusing several sub-processes, or as part of a larger macro process.

While the invention has been described with reference to numerousspecific details, one of ordinary skill in the art will recognize thatthe invention can be embodied in other specific forms without departingfrom the spirit of the invention. In addition, a number of the figuresconceptually illustrate processes. The specific operations of theseprocesses may not be performed in the exact order shown and described.The specific operations may not be performed in one continuous series ofoperations, and different specific operations may be performed indifferent embodiments. Furthermore, the process could be implementedusing several sub-processes, or as part of a larger macro process. Thus,one of ordinary skill in the art would understand that the invention isnot to be limited by the foregoing illustrative details, but rather isto be defined by the appended claims.

1. (canceled)
 2. A system for displaying navigation instructions on adevice, the system comprising: one or more processors; a display screen;and a non-transitory machine-readable medium storing a program whichwhen executed by at least one of the one or more processors providesnavigation instructions on the display screen, the program comprisingsets of instructions for: receiving a message while the display screenis turned off and the device is in a locked mode; automatically turningon the display screen; displaying a message notification on a displayarea of the display screen for a preset length of time; after the presetlength of time, removing the message notification from the display area;receiving a touch gesture on the display screen without unlocking thedevice; and in response to receiving the touch gesture, displaying themessage without unlocking the device.
 3. The system of claim 2, whereinthe touch gesture comprises a downward swipe on the display screen. 4.The system of claim 2, wherein the touch gesture comprises a single tapor a double tap on the display screen.
 5. The system of claim 2, whereinthe program further comprises instructions for: displaying a selectablemessage access control, wherein the touch gesture further comprisestouching the message access control.
 6. The system of claim 2, whereinthe message notification is a first message notification and the messageis a first message, the program further comprising instructions fordisplaying a second message notification before receiving the touchgesture and displaying both the first message and the second messageafter receiving the touch gesture.
 7. The system of claim 2, the programfurther comprising instructions for: after displaying the message,receiving a command to stop displaying the message.
 8. The system ofclaim 2, wherein when the device is in the locked mode, access isprevented to a plurality of applications installed on a non-transitorymachine-readable medium until an input to unlock the device is received.9. The system of claim 2, wherein providing navigation instructionscomprise displaying a map on the display screen, and the message isdisplayed as translucent, semi-transparent, or transparent, allowing themap to be seen through the message.
 10. A method of displaying messagesreceived in a locked mode of a device with a display screen, the methodcomprising: receiving a message while the display screen is turned offand the device is in a locked mode; automatically turning on the displayscreen; displaying a message notification on a display area of thedisplay screen for a preset length of time; after the preset length oftime, removing the message notification from the display area; receivinga touch gesture on the display screen without unlocking the device; andin response to receiving the touch gesture, displaying the messagewithout unlocking the device.
 11. The method of claim 10, wherein thetouch gesture comprises a downward swipe on the display screen.
 12. Themethod of claim 10, wherein the touch gesture comprises a single tap ora double tap on the display screen.
 13. The method of claim 10, furthercomprising: displaying a selectable message access control, wherein thetouch gesture further comprises touching the message access control. 14.The method of claim 10, wherein the message notification is a firstmessage notification and the message is a first message, and furthercomprising: displaying a second message notification before receivingthe touch gesture and displaying both the first message and the secondmessage after receiving the touch gesture.
 15. The method of claim 10,further comprising: after displaying the message, receiving a command tostop displaying the message.
 16. The method of claim 10, wherein whenthe device is in the locked mode, access is prevented to a plurality ofapplications installed on the device until an input to unlock the deviceis received.
 17. The method of claim 10, wherein providing navigationinstructions comprises displaying a map on the display screen, and themessage is displayed as translucent, semi-transparent, or transparent,allowing the map to be seen through the message.
 18. A non-transitorymachine-readable medium storing a program which when executed by atleast one processing unit provides navigation directions for a devicecomprising a display screen, the program comprising sets of instructionsfor: receiving a message while the display screen is turned off and thedevice is in a locked mode; automatically turning on the display screen;displaying a message notification on a display area of the displayscreen for a preset length of time; after the preset length of time,removing the message notification from the display area; receiving atouch gesture on the display screen without unlocking the device; and inresponse to receiving the touch gesture, displaying the message withoutunlocking the device.
 19. The non-transitory machine-readable medium ofclaim 18, wherein the touch gesture comprises a downward swipe on thedisplay screen.
 20. The non-transitory machine-readable medium of claim18, wherein the touch gesture comprises a single tap or a double tap onthe display screen.
 21. The non-transitory machine-readable medium ofclaim 18, further comprising: displaying a selectable message accesscontrol, wherein the touch gesture further comprises touching themessage access control.
 22. The non-transitory machine-readable mediumof claim 18, wherein the message notification is a first messagenotification and the message is a first message, and further comprising:displaying a second message notification before receiving the touchgesture and displaying both the first message and the second messageafter receiving the touch gesture.
 23. The non-transitorymachine-readable medium of claim 18, further comprising: afterdisplaying the message, receiving a command to stop displaying themessage.
 24. The non-transitory machine-readable medium of claim 18,wherein when the device is in the locked mode, access is prevented to aplurality of applications stored on the device until an input to unlockthe device is received.
 25. The non-transitory machine-readable mediumof claim 18, wherein providing navigation instructions comprisesdisplaying a map on the display screen, and the message is displayed astranslucent, semi-transparent, or transparent, allowing the map to beseen through the message.